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.
Description of problem:
The prepboot partition is required for ppc64le installations. When added to a kickstart this partition was created as sda5, not sda1, and is not in the /root/anaconda-ks.cfg
Version-Release number of selected component (if applicable):
RHEL 8.4
How reproducible:
Steps to Reproduce:
1. part prepboot --fstype "PPC PReP Boot" --size=10 --ondisk=/dev/disk/by-path/pci-0001:12:00.0-scsi-0:2:0:0
2.
3.
Actual results:
# grep -r "pci-0001:12:00.0-scsi-0:2:0:0"sos_commands/block/ls_-lanR_.dev
lrwxrwxrwx. 1 0 0 9 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0 -> ../../sda
lrwxrwxrwx. 1 0 0 10 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0-part1 -> ../../sda1
lrwxrwxrwx. 1 0 0 10 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0-part2 -> ../../sda2
lrwxrwxrwx. 1 0 0 10 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0-part3 -> ../../sda3
lrwxrwxrwx. 1 0 0 10 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0-part4 -> ../../sda4
lrwxrwxrwx. 1 0 0 10 Jun 10 01:30 pci-0001:12:00.0-scsi-0:2:0:0-part5 -> ../../sda5 <<PrepBoot partition created here
# grep sda sos_commands/block/lsblk
sda 8:0 0 1.1T 0 disk
|-sda1 8:1 0 500M 0 part /boot
|-sda2 8:2 0 265G 0 part
|-sda3 8:3 0 48.8G 0 part
|-sda4 8:4 0 4K 0 part
`-sda5 8:5 0 10M 0 part
# grep -c prep root/anaconda-ks.cfg
0
Expected results:
The PReP boot partition should be sda1 and it should be in the /root/anaconda-ks.cfg file
Additional info:
================Documentation=======================
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index
- - - - - - - - -
B.5.15. reqpart
The reqpart Kickstart command is optional. It automatically creates partitions required by your hardware platform. These include a /boot/efi partition for systems with UEFI firmware, a biosboot partition for systems with BIOS firmware and GPT, and a PRePBoot partition for IBM Power Systems.
- - - - - - - - -
PReP boot partition - recommended size of 4 to 8 MiB
When installing Red Hat Enterprise Linux on IBM Power System servers, the first partition of the hard drive should include a PReP boot partition. This contains the GRUB2 boot loader, which allows other IBM Power Systems servers to boot Red Hat Enterprise Linux.
The same syntax works in 8.2 (8.3 has not yet been tested)
What is the impact of this bug? Is such a system unable to boot? I'm asking because based on the logs, the system is PowerNV - and these systems do not require the Prepboot partition. See related bugs 1853619,1873236.
Well then. I seem to need to improve my bug search skills.
Since thats the case, can we get the documentation updated to reflect that? I can open a new bug if thats best to have a note that PowerNV does not require prepboot
**the system is booting and functional
OK, moving this bug to Documentation.
There are several places talking about "PReP" partitions in the installation guides, so there should be notes that such a partition is not required on PowerNV systems.