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 updating a paravirtualized Xen guest that boots using PyGrub from RHEL 7.0 to 7.1, grubby-8.28-11.el7.x86_64 fails to insert the initrd into /boot/grub/grub.conf. I can provide the Xen PV template that we use if it would help with troubleshooting this issue further.
Version-Release number of selected component: grubby-8.28-11.el7.x86_64
How reproducible: I'm able to reproduce this in 100% of upgrades from 7.0 to 7.1.
Steps to Reproduce:
1. Install RHEL 7.0 paravirtualized Xen guest that uses grub legacy boot files via PyGrub.
2. yum update
3. Reboot
Actual results:
System kernel panics as it can't find a disk, and /boot/grub/grub.conf is missing the initrd. Adding the initrd allows the system to boot again.
Expected results:
/boot/grub/grub.conf contains a proper initrd line and the system boots successfully.
Additional comments:
grubby-8.28-8.el7.x86_64, which is the RHEL 7.0 version, seems to work correctly. As a temporary workaround I've excluded grubby in yum.conf, and the yum update process correctly installs the kernel when upgrading from 7.0 to 7.1.
If I'm missing anything important please let me know and I'll provide whatever additional information is needed.
Any chance one of you can try this with the 8.40-1 package in Fedora? I suspect this is the same bug that causes #1204353 , #1204888 , #1206943 , and #1152152 .
Also got this after upgrading to 7.1 on KVM. Downgrading and excluding grubby avoided the issue for now. Thank you for the info.
This should be elevated since anyone who upgraded from 6 to 7 have/will hit this and now that this venom thing is wild reboots will occur sooner than later. Others like the OP have this issue because their EL 7 template has legacy grub instead of grub2.
Given the descriptions in this bug and personal experience, to reproduce (not tested):
1. Install EL 6 on any hardware/hypervisor
2. Upgrade to EL 7.0
3. Reboot, everything should be fine
4. yum update to EL 7.1
5. grub.conf should have EL 7.1 kernel without initrd
All previous kernels in grub.conf are unaffected, only new inserts with the EL 7.1 grubby fail.
Yes, those are the current 7.2 packages from these erratum:
RHBA-2015:21032 - grubby-8.28-12.el7
RHBA-2015:21033 - grub2-2.02-0.22.el7 (which has supplanted -0.17.el7 )
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, 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://rhn.redhat.com/errata/RHBA-2015-2110.html
This has most definitely not been fixed with the latest grubby. We're able to reproduce the issue on command by building a RHEL 7.1 box, then running `yum update redhat-release-server kernel`. Running a `yum update grubby grub2 grub2-tools` does not change the outcome (verified post yum update that grubby is at -17).
Contacted RHEL support to work on this case, will post the new bug id for those finding this ticket via search.