RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If "autopart" is used as a kickstart parameter, the LVM volume group is spread across all disks.

On a system which has LUNs presented from shared storage, this means that the VG may be spread across 20+ disks, rather than just local disks.

Version-Release number of selected component (if applicable):
All

How reproducible:
100%

Steps to Reproduce:
1. Use 'autopart' in kickstart on a system with a large number of LUNs/disks presented
2.
3.

Actual results:
The VG is spread across all disks

Expected results:
'autopart' should have a flag which specifies that only some disks should be used, or all disks which are not multipathed

Additional info:

Isn't this what the "ignoredisk" kickstart command[0] already does ?

[0] http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id20

You're right -- I missed "--onlyuse"

Tested and verified that this works.

We just need to add this to the documentation for RHV.

Ying: can we test upgrade speeds on a system with a large number of LUNs after installing with "--onlyuse sda" ?

Ryan, 
QE can test upgrade speeds after installing with "--onlyuse sda". Right now, the largest local disk is about 3T in QE testing environment. We will try this disk firstly to see the upgrade speed, then we will try to find a larger disk, if possible, to test the upgrade speed.