Bug 1442117
| Summary: | new-kernel-pkg doesn't copy custom initrd overlays from default kernel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Škarvada <jskarvad> |
| Component: | grubby | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | atragler, jhsiao, jskarvad, jstodola, lcapitulino, pjones, rharwood |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-01-15 07:34:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1394932 | ||
|
Description
Jaroslav Škarvada
2017-04-13 14:54:38 UTC
Kernel package calls new-kernel-pkg from its %post. From the following list looks like my system doesn't have the issue: [root@netqe5 ~]# grep initrd16 /boot/grub2/grub.cfg initrd16 /initramfs-3.10.0-648.el7.x86_64.img $tuned_initrd initrd16 /initramfs-3.10.0-514.el7.x86_64.img $tuned_initrd initrd16 /initramfs-3.10.0-643.el7.x86_64.img $tuned_initrd Right ? (In reply to Jean-Tsung Hsiao from comment #5) > From the following list looks like my system doesn't have the issue: > > [root@netqe5 ~]# grep initrd16 /boot/grub2/grub.cfg > initrd16 /initramfs-3.10.0-648.el7.x86_64.img $tuned_initrd > initrd16 /initramfs-3.10.0-514.el7.x86_64.img $tuned_initrd > initrd16 /initramfs-3.10.0-643.el7.x86_64.img $tuned_initrd > > Right ? This is correct result, but please note the correct reproducer: - # systemctl stop tuned # to be safe otherwise Tuned may add it to the grub.cfg when it's restarted or Tuned profile is changed - make sure you have some older kernel installed and booted with $tuned_initrd in initrd16 and no newer kernel is listed in grub.cfg - upgrade kernel - check the grub.cfg, you should find entries of initrd16 without $tuned_initrd for new kernel (In reply to Jaroslav Škarvada from comment #6) > (In reply to Jean-Tsung Hsiao from comment #5) > > From the following list looks like my system doesn't have the issue: > > > > [root@netqe5 ~]# grep initrd16 /boot/grub2/grub.cfg > > initrd16 /initramfs-3.10.0-648.el7.x86_64.img $tuned_initrd > > initrd16 /initramfs-3.10.0-514.el7.x86_64.img $tuned_initrd > > initrd16 /initramfs-3.10.0-643.el7.x86_64.img $tuned_initrd > > > > Right ? > > This is correct result, but please note the correct reproducer: > > - # systemctl stop tuned # to be safe otherwise Tuned may add it to the > grub.cfg when it's restarted or Tuned profile is changed > > - make sure you have some older kernel installed and booted with > $tuned_initrd in initrd16 and no newer kernel is listed in grub.cfg > > - upgrade kernel > > - check the grub.cfg, you should find entries of initrd16 without > $tuned_initrd for new kernel If you reboot after the kernel is upgraded (or restart Tuned) you will end up with correct result, because it's workaround in Tuned to patch the grub.cfg and add the missing $tuned_initrd when it's started Further testing shows that: *** Right after kernel update *** [root@netqe6 yum.repos.d]# grep initrd16 /boot/grub2/grub.cfg initrd16 /initramfs-3.10.0-655.el7.x86_64.img initrd16 /initramfs-3.10.0-648.el7.x86_64.img $tuned_initrd initrd16 /initramfs-3.10.0-643.el7.x86_64.img $tuned_initrd *** After reboot *** grep initrd16 /boot/grub2/grub.cfg initrd16 /initramfs-3.10.0-655.el7.x86_64.img $tuned_initrd initrd16 /initramfs-3.10.0-648.el7.x86_64.img $tuned_initrd initrd16 /initramfs-3.10.0-643.el7.x86_64.img $tuned_initrd So, are we having a bug ? Got it --- tuned is doing a work-around. Yes. Tuned is updating grub.cfg when it's activated during boot and it sees that the initrd image is missing from the initrd16 line. However, you have to reboot a second time. There are two problems with that. First, people may not reboot a second time. Secondly, there's no indication that something went wrong. People will only notice they have a problem if/when they get drops. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |