1. Proposed title of this feature request
[RFE] Provide RHV-M Appliance image with LVM partitioning
2. What is the nature and description of the request?
Difficulties to extend partitions in the Engine VM created from the RHV-M Appliance.
3. Why does the customer need this? (List the business requirements here)
Customer needs in order to avoid loosing data trying to resize a non-LVM partition.
4. How would the customer like to achieve this? (List the functional requirements here)
Customer wants the possibility to deploy the RHV-M Appliance image provided in Customer Portal with LVM partitioning.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Can be tested by deploying the image provided and checking if the partitioning was made using LVM.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No.
8. Is the sales team involved in this request and do they have any additional input?
No.
9. List any affected packages or components.
RHV-M Appliance image provided in Customer Portal.
Given that cloud-utils-growpart does not support LVM, and the kickstart is only used during image creation, I'm not sure what the goal is here. Can you clarify?
cloud-utils-growpart requires not using LVM, and expands the last partition on disk
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:1088