Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
Comparing with rhel guest image, azure image and amazon linux ec2 image, there is extra 'rescue' boot entry in rhel ec2 images.
If there is no specific reason to do this, I am suggesting to exclude this pkg in ec2 image.
This will release about 80M space from boot partition and keep consistent with rhel guest and azure image.

# rpm -qa "*rescue*"
dracut-config-rescue-055-30.git20220216.el9.x86_64
# grubby --info=3
index=3
kernel="/boot/vmlinuz-0-rescue-ffffffffffffffffffffffffffffffff"
args="console=ttyS0,115200n8 console=tty0 net.ifnames=0 rd.blacklist=nouveau nvme_core.io_timeout=4294967295"
root="UUID=da88f4cb-fcdd-4f87-9eb7-40155e2c75bc"
initrd="/boot/initramfs-0-rescue-ffffffffffffffffffffffffffffffff.img"
title="Red Hat Enterprise Linux (0-rescue-ffffffffffffffffffffffffffffffff) 9.0 (Plow)"
id="ffffffffffffffffffffffffffffffff-0-rescue"

RHEL Version:
RHEL-9.0(5.14.0-70.el9)

How reproducible:
100%

Steps to Reproduce:
1. Check the boot entry in rhel9 images

Actual results:
has rescue boot entry in ec2 image

Expected results:
remove rescue boot entry

Additional info:
- N/A

Hi Vitaly,

I guess it is safe to remove this pkg from ec2 image, please double confirm. Thanks

I agree, cloud instances are normally "rescued" in a different way: by connecting block volume
to some other working instance.

Hi @igulina

Do you see any issue with the proposed change (basically to exclude `dracut-config-rescue` package from the default image package set) for the EC2 SAP image?

-------------------------------------------------------

In addition, the same situation applied to RHEL-8 EC2 images. Should we change them as well in 8.7?

igulina confirmed that the package can be indeed removed. We should be good to go then.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: Image Builder security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7950