Bug 1730655 - 51-dracut-rescue-postinst.sh adds a Rescue entry that will become the default if saved_entry is not set
Summary: 51-dracut-rescue-postinst.sh adds a Rescue entry that will become the default...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grubby
Version: 7.6
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-17 09:34 UTC by Welterlen Benoit
Modified: 2020-02-13 17:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Welterlen Benoit 2019-07-17 09:34:56 UTC 
Description of problem:
A customer faced the situation where an upgrade of the kernel set the default grub entry to the Rescue. 
I think that even if there is no saved_entry, the Rescue should be put under any other entry. 

Version-Release number of selected component (if applicable):
- RHEL 7
- dracut-config-rescue-033-554.el7.x86_64

How reproducible:
Always if:
- The issue is the combination of 2 situations:
- no /etc/machine-id (or new one created for any reason, that does not match the rescue initramfs in /boot)
- no saved_entry in grubenv

Steps to Reproduce:
1. rm /etc/machine-id
2. delete saved_entry in grubenv
3. update kernel

Actual results:
The default entry is the Rescue one.

Expected results:
The default entry should be the new kernel installed

Additional info:
Comment 3 Lukáš Nykrýn 2019-07-30 13:08:05 UTC 
I am not sure that dracut can influence that. new-kernel-pkg belongs to grubby, so let's try it there.
Note You need to log in before you can comment on or make changes to this bug.