Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 865495[details]
The script in %pre
Description of problem:
Creating a partition using parted in the %pre section of the kickstart doesn't allow anaconda to see the disks that it has created.
Many debugs to the stdout by cat /proc/partitions within the %pre section, showed that the partitions in-fact were created.
After rebooting the node, I was able to install on the same disks without re-creating the partitions using the same kickstart file, without the parted commands included in the script.
Version-Release number of selected component (if applicable):
How reproducible:
Everytime
Steps to Reproduce:
1. Create a standard kickstart file
2. Instead of the partitioning add %include /tmp/partitionfile
3. include the attached script to the %pre section
4. Install the machine using the kickstart file
Actual results:
Anaconda is not able to see the disks, and we see the following output on the screen
Specified nonexistent partition sda1 in partition command
Expected results:
The installation should see the partition, and continue to install
Additional info:
Created attachment 865495 [details] The script in %pre Description of problem: Creating a partition using parted in the %pre section of the kickstart doesn't allow anaconda to see the disks that it has created. Many debugs to the stdout by cat /proc/partitions within the %pre section, showed that the partitions in-fact were created. After rebooting the node, I was able to install on the same disks without re-creating the partitions using the same kickstart file, without the parted commands included in the script. Version-Release number of selected component (if applicable): How reproducible: Everytime Steps to Reproduce: 1. Create a standard kickstart file 2. Instead of the partitioning add %include /tmp/partitionfile 3. include the attached script to the %pre section 4. Install the machine using the kickstart file Actual results: Anaconda is not able to see the disks, and we see the following output on the screen Specified nonexistent partition sda1 in partition command Expected results: The installation should see the partition, and continue to install Additional info: