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:
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:

I am not sure that dracut can influence that. new-kernel-pkg belongs to grubby, so let's try it there.

Closing the bug as the attached customer case is closed.