Hide Forgot
Description of problem: The system is managed by Satellite 5.6. with auto errata update "yes". After the auto-update from RHEL 7.3 to RHEL 7.4. initramfs-3.10.0-693.1.1.el7.x86_64.img is missing. Rebooting with the new kernel fails. Version-Release number of selected component (if applicable): - RHEL 7.4 - kernel-3.10.0-693.1.1.el7.x86_64 - initramfs-3.10.0-693.1.1.el7.x86_64.img Steps to Reproduce: 1. System gets updated by Satellite 5.6 (auto errata update) 2. initramfs-3.10.0-693.1.1.el7.x86_64.img is missing 3. reboot to kernel-3.10.0-693.1.1.el7.x86_64 fails Actual results: initramfs-3.10.0-693.1.1.el7.x86_64.img is missing and reboot fails Expected results: initramfs-3.10.0-693.1.1.el7.x86_64.img gets generated with the installation of kernel-3.10.0-693.1.1.el7.x86_64 Additional info: A workaround, reported by the customer, is to reinstall the kernel manually. This will create the initramfs file. Also, I executed 'yum update kernel' manually on a RHEL 7.3 testsystem, kernel-3.10.0-693.1.1.el7.x86_64 was installed and initramfs-3.10.0-693.1.1.el7.x86_64.img generated. Maybe this relates to Satellite 5.6?
We can confirm this. Updating kernel rpm via rhnsd/rhn_check kernel postscript will failed or exit too early? Aug 29 04:12:26 xxxxx rhnsd[37288]: running program /usr/sbin/rhn_check with PID 37288 Aug 29 04:12:50 xxxxx dracut: dracut- without further output like xxxxx dracut: Executing: /sbin/dracut -f /boot/initramfs-3.10.0-693.1.1.el7.x86_64.img 3.10.0-693.1.1.el7.x86_64
redhat-upgrade-dracut is used only by redhat-upgrade-tool whose only purpose is to perform upgrades from major version of the system to a new major version, at this time only from RHEL 6 to RHEL 7. This bug would belong to the redhat-upgrade-dracut component only if you used Red Hat Upgrade Tool to upgrade from RHEL 6 to RHEL 7 and you think this upgrade didn't end up well causing the problems with missing kernel when updating RHEL 7.3 to 7.4. Otherwise I think this bug belongs either to the 'dnf' or 'dracut' component.
There's no 'dnf' on RHEL 7 but 'yum' instead, of course.
Customer reported, that this also *somtimes* happens when manually executing 'yum update' - independent from Satellite 5.6 with auto-update. As before, a reinstall of the kernel solves the issue (creates initramfs...).
*** Bug 1490812 has been marked as a duplicate of this bug. ***
If a customer has a stable reproducer, can they please add debug=yes to /etc/dracut.conf, try the update and post here output of journalctl?
Also can you please check that this is not a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1475039
RHEL Support just told me I have this bug. "Hello, Now initramfs for latest kernel is present in /boot/grub2/grub.cfg and /boot/. Seems you are hitting a known bug Bug 1484430 - After auto-update to RHEL 7.4, initramfs file is missing for new kernel https://bugzilla.redhat.com/show_bug.cgi?id=1484430 I am moving this case to satellite team they can better suggest you for prevention or any other workaround. We use Satellite 5.6 we are not using upgraded systems. These are RHEL7 the entire time. Also this causes kernel Panics when rebooted. They are fixed when the kernel is installed. But we also would like to know how to prevent it since we have 200 more servers to patch, and we dont know what is triggering it.
(In reply to JB from comment #25) > RHEL Support just told me I have this bug. > > "Hello, > > Now initramfs for latest kernel is present in /boot/grub2/grub.cfg and > /boot/. Seems you are hitting a known bug > > Bug 1484430 - After auto-update to RHEL 7.4, initramfs file is missing for > new kernel > https://bugzilla.redhat.com/show_bug.cgi?id=1484430 > > I am moving this case to satellite team they can better suggest you for > prevention or any other workaround. > > We use Satellite 5.6 we are not using upgraded systems. These are RHEL7 the > entire time. Also this causes kernel Panics when rebooted. > > They are fixed when the kernel is installed. But we also would like to know > how to prevent it since we have 200 more servers to patch, and we dont know > what is triggering it. When the kernel is re-installed that is, it is corrected.