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.
Bug 1442117 - new-kernel-pkg doesn't copy custom initrd overlays from default kernel
Summary: new-kernel-pkg doesn't copy custom initrd overlays from default kernel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grubby
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1394932
TreeView+ depends on / blocked
 
Reported: 2017-04-13 14:54 UTC by Jaroslav Škarvada
Modified: 2022-01-14 19:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:34:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jaroslav Škarvada 2017-04-13 14:54:38 UTC 
Description of problem:
E.g. we have the following in grub.cfg:

initrd16 /initramfs-3.10.0-349.el7.x86_64.img $tuned_initrd

After kernel upgrade there is:
initrd16 /initramfs-3.10.0-647.el7.x86_64.img

I.e. the custom initrd overlay is not copied, i.e. there should be:
initrd16 /initramfs-3.10.0-647.el7.x86_64.img $tuned_initrd

Version-Release number of selected component (if applicable):
grubby-8.28-23.el7

How reproducible:
Always

Steps to Reproduce:
1. Have initrd16 entry with custom initrd overlay(s)
2. Update kernel

Actual results:
New kernel doesn't have the custom initrd overlay

Expected results:
New kernel has the custom initrd overlay

Additional info:
Comment 2 Jaroslav Škarvada 2017-04-13 14:57:13 UTC 
Kernel package calls new-kernel-pkg from its %post.
Comment 5 Jean-Tsung Hsiao 2017-04-21 13:35:27 UTC 
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 ?
Comment 6 Jaroslav Škarvada 2017-04-21 13:52:16 UTC 
(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
Comment 7 Jaroslav Škarvada 2017-04-21 13:54:44 UTC 
(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
Comment 8 Jean-Tsung Hsiao 2017-04-21 14:10:49 UTC 
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 ?
Comment 9 Jean-Tsung Hsiao 2017-04-21 14:15:49 UTC 
Got it --- tuned is doing a work-around.
Comment 10 Luiz Capitulino 2017-04-24 13:04:37 UTC 
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.
Comment 14 RHEL Program Management 2021-01-15 07:34:04 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.