Bug 2227085

1. Proposed title of this feature request

Check volume group names within the %pre section of the kickstart

2. Who is the customer behind the request?

Account: Red Hat - Confirmed Stateside Support	6907590	
TAM customer: no
CSM customer: no
Strategic: no

3. What is the nature and description of the request?

We have a customized kickstart. The challenge we are facing is that during the PRE% section of the kickstart, we are enumerating scsi block devices for our customer to select a target disk to install to. However, whenever we run any LVM commands they all return nothing but the moment the Anaconda graphical install starts then we are able to see the LVM devices on the existing hard drive (ie any LVM volumes that were created from a previous OS installation)..

We are using the dialog command to ask the user which disk to install to and looking for the LVM information on every disk prior to the dialog prompt so they can easily identify which drive they want to install to.

How do we get the LVM functionality in the pre% section of the kickstart?

4. Why does the customer need this? (List the business requirements here)

In the %Pre section of the kickstart is the ideal time to layout partitions and include them later in the script.  When using the DISA Stig security profile you have to have a very specific layout before the anaconda gui loads.  If you don't have it just right then it will fail, and the user will need to fix it.  

We are developing a kickstart that allows the user to select what disk they want to install to.  If the volume group already exists on a disk other than that which we are wiping and installing to the install will halt until the user fixes it.  This can be fixed by checking to see if the volume group already exists before we try to use it.  If the volume group does exist we come up with a different name and check it automatically.  This doesn't work though because vgs and vgdisplay returns nothing.

5. How would the customer like to achieve this? (List the functional requirements here)

Modifications to kickstart %Pre functionality

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Customer has kickstart listed in the case which is non-functional due to above mentioned issue. 

7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 

N/A

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?  

ASAP

9. Is the sales team involved in this request and do they have any additional input? 

No

10. List any affected packages or components.

kickstart
lvm2

11. Would the customer be able to assist in testing this functionality if implemented?

Likely