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:
-----------------------
When we run the livemedia-creator command to generate a LiveOS on a ppc64le server, we can't boot the LiveOS successfully in a ppc64le server.
The grub.cfg.in provides a wrong initrd and vmlinuz path ppc/ppc/initrd.img actually it is located in ppc/ppc64/ directory. After we modify the /usr/share/lorax/tempates.d/80-rhel/live/config_files/ppc/grub.cfg.in file and rerun the livemedia-creator command to generate a new LiveOS iso image file, it is successful.
Version-Release number of selected component (if applicable):
-----------------------
lorax-19.7.28-1.el7.ppc64.rpm
How reproducible:
------------------
- Install lorax
- Run the livemedia-creator command to generate a LiveOS on a ppc64le server.
-
Additional Info:
---------------
[1] Mounted rhel-8.4-ppc64le-boot.iso on /mnt and checked the tree
$ ll /mnt/ppc/
total 17
-r--r--r--. 1 root root 12520 Dec 10 2020 bootinfo.txt
-r--r--r--. 1 root root 1355 Dec 10 2020 mapping
dr-xr-xr-x. 2 root root 2048 May 3 20:40 ppc64
-r--r--r--. 1 root root 660 May 3 20:40 TRANS.TBL
$ ll /mnt/ppc/ppc64/
total 89353
-r--r--r--. 1 root root 61566636 May 3 20:40 initrd.img
-r--r--r--. 1 root root 441 May 3 20:40 TRANS.TBL
-r-xr-xr-x. 1 root root 29929397 Apr 29 14:59 vmlinuz
--> It's clearly ppc/ppc64/ directory where kernel/initrd live
[2] Installed lorax and checked the template:
vim /usr/share/lorax/templates.d/80-rhel/live/config_files/ppc/grub.cfg.in
There we cam see "${2}" and "${BITS}", compared with customer's modifications:
$ diff -u 0010-grub.cfg.in 0020-grub.cfg.in.modified
--- 0010-grub.cfg.in 2021-10-13 07:12:54.000000000 +0000
+++ 0020-grub.cfg.in.modified 2021-10-13 07:15:53.000000000 +0000
@@ -6,13 +6,13 @@
for BITS in 32 64; do
if [ -d "/ppc/ppc${BITS}" ]; then
menuentry "Start @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os {
- linux /ppc/ppc${2}/vmlinuz @ROOT@ @EXTRA@ ro rd.live.image quiet
- initrd /ppc/ppc${2}/initrd.img
+ linux /ppc/ppc${BITS}/vmlinuz @ROOT@ @EXTRA@ ro rd.live.image quiet
+ initrd /ppc/ppc${BITS}/initrd.img
}
menuentry "Test this media & start @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os {
- linux /ppc/ppc${2}/vmlinuz @ROOT@ @EXTRA@ rd.live.image rd.live.check ro quiet
- initrd /ppc/ppc${2}/initrd.img
+ linux /ppc/ppc${BITS}/vmlinuz @ROOT@ @EXTRA@ rd.live.image rd.live.check ro quiet
+ initrd /ppc/ppc${BITS}/initrd.img
}
fi
done
--> Clearly ${2} is a typo and should be changed by ${BITS}, as the customer did.
Tested with lorax-templates-rhel-8.6-1.el8, the kernel and initrd paths are set correctly to /ppc/ppc64/... in grub2 and the live media boots successfully.
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 (lorax-templates-rhel bug fix and enhancement update), 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-2022:1787
Description of problem: ----------------------- When we run the livemedia-creator command to generate a LiveOS on a ppc64le server, we can't boot the LiveOS successfully in a ppc64le server. The grub.cfg.in provides a wrong initrd and vmlinuz path ppc/ppc/initrd.img actually it is located in ppc/ppc64/ directory. After we modify the /usr/share/lorax/tempates.d/80-rhel/live/config_files/ppc/grub.cfg.in file and rerun the livemedia-creator command to generate a new LiveOS iso image file, it is successful. Version-Release number of selected component (if applicable): ----------------------- lorax-19.7.28-1.el7.ppc64.rpm How reproducible: ------------------ - Install lorax - Run the livemedia-creator command to generate a LiveOS on a ppc64le server. - Additional Info: --------------- [1] Mounted rhel-8.4-ppc64le-boot.iso on /mnt and checked the tree $ ll /mnt/ppc/ total 17 -r--r--r--. 1 root root 12520 Dec 10 2020 bootinfo.txt -r--r--r--. 1 root root 1355 Dec 10 2020 mapping dr-xr-xr-x. 2 root root 2048 May 3 20:40 ppc64 -r--r--r--. 1 root root 660 May 3 20:40 TRANS.TBL $ ll /mnt/ppc/ppc64/ total 89353 -r--r--r--. 1 root root 61566636 May 3 20:40 initrd.img -r--r--r--. 1 root root 441 May 3 20:40 TRANS.TBL -r-xr-xr-x. 1 root root 29929397 Apr 29 14:59 vmlinuz --> It's clearly ppc/ppc64/ directory where kernel/initrd live [2] Installed lorax and checked the template: vim /usr/share/lorax/templates.d/80-rhel/live/config_files/ppc/grub.cfg.in There we cam see "${2}" and "${BITS}", compared with customer's modifications: $ diff -u 0010-grub.cfg.in 0020-grub.cfg.in.modified --- 0010-grub.cfg.in 2021-10-13 07:12:54.000000000 +0000 +++ 0020-grub.cfg.in.modified 2021-10-13 07:15:53.000000000 +0000 @@ -6,13 +6,13 @@ for BITS in 32 64; do if [ -d "/ppc/ppc${BITS}" ]; then menuentry "Start @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os { - linux /ppc/ppc${2}/vmlinuz @ROOT@ @EXTRA@ ro rd.live.image quiet - initrd /ppc/ppc${2}/initrd.img + linux /ppc/ppc${BITS}/vmlinuz @ROOT@ @EXTRA@ ro rd.live.image quiet + initrd /ppc/ppc${BITS}/initrd.img } menuentry "Test this media & start @PRODUCT@ @VERSION@ (${BITS}-bit kernel)" $BITS --class fedora --class gnu-linux --class gnu --class os { - linux /ppc/ppc${2}/vmlinuz @ROOT@ @EXTRA@ rd.live.image rd.live.check ro quiet - initrd /ppc/ppc${2}/initrd.img + linux /ppc/ppc${BITS}/vmlinuz @ROOT@ @EXTRA@ rd.live.image rd.live.check ro quiet + initrd /ppc/ppc${BITS}/initrd.img } fi done --> Clearly ${2} is a typo and should be changed by ${BITS}, as the customer did.