-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.5
-
None
-
No
-
None
-
rhel-sst-image-builder
-
None
-
False
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
x86_64
-
None
What were you trying to do that didn't work?
I am deploying RHEL 9 in the azure cloud. I've noticed that the defaults of the golden images (byos and payg) do not adhere to the stated rhel minimums from the docs:
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html-single/interactively_installing_rhel_from_installation_media/index#recommended-partitioning-scheme_manual-partitioning
it states that /boot should be at least 1G, on azure-rhel8 it's 496M on azure-rhel9 it's 436M. I am guessing it's easy to remedy for new images, there is enough space on the disk, by default rhel gets installed on a 64G disk on azure.
What is the impact of this issue to you?
Looking at the RHEL9 servers I have the space is fairly tight for the default of keeping 3 kernels +kdump initramfs (and having the space to install another one during updates).
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
always
Steps to reproduce
- Install a rhel 9/8 payg/byos golden images in azure
Expected results
have /boot with 1G
Actual results
have /boot with less
- is related to
-
RHELDOCS-20194 Increase recommended size of /boot in Azure deployment guide
-
- Closed
-