Bug 2064087

Summary:	suggest to exclude dracut-config-rescue in rhel ec2 images
Product:	Red Hat Enterprise Linux 9	Reporter:	Frank Liang <xiliang>
Component:	osbuild-composer	Assignee:	Tomáš Hozza <thozza>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0	CC:	atodorov, eterrell, igulina, jabia, jrusz, linl, nmunoz, obudai, qzhang, thozza, vkuznets, wshi, ymao, yuxisun
Target Milestone:	rc	Keywords:	Patch, Triaged, Upstream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	osbuild-composer-59-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 09:50:32 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:

Description Frank Liang 2022-03-15 02:43:30 UTC

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

Comment 1 Frank Liang 2022-03-15 02:47:17 UTC

Hi Vitaly,

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

Comment 2 Vitaly Kuznetsov 2022-03-15 08:40:28 UTC

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

Comment 3 Tomáš Hozza 2022-03-15 10:32:33 UTC

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?

Comment 6 Ondřej Budai 2022-07-20 11:38:21 UTC

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

Comment 13 errata-xmlrpc 2022-11-15 09:50:32 UTC

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