-
Bug
-
Resolution: Done-Errata
-
Minor
-
None
-
rhel-8.10, rhel-9.4
-
None
-
Low
-
rhel-sst-image-builder
-
ssg_front_door
-
3
-
False
-
-
None
-
None
-
-
All
-
None
What were you trying to do that didn't work?
Current RHEL AMIs has two console parameters 'console=ttyS0,115200n8 console=tty0', which set tty0 as primary console. So we have less information printed than RHEL guest image, Amazon Linux and Ubuntu during boot. To keep this setting consistent with rhel guest image and make it more useful for boot debug, I am suggesting set ttyS0 as primary console.
// RHEL-9.4 Beta AMIs # cat /proc/cmdline BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.14.0-427.el9.x86_64 root=UUID=f9e543b4-c517-4c6b-98ae-948c023183ef console=ttyS0,115200n8 console=tty0 net.ifnames=0 rd.blacklist=nouveau nvme_core.io_timeout=4294967295 crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M //RHEL guest image # cat /etc/default/grub GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto" //Ubuntu 22.04 # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-1014-aws root=PARTUUID=a21bf548-7951-497e-9d37-d52953e74c21 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 //Amazon Linux $ cat /proc/cmdline BOOT_IMAGE=(hd0,gpt1)/boot/vmlinuz-6.1.82-99.168.amzn2023.x86_64 root=UUID=3d668946-b9eb-4d6b-acbd-da437d796ee8 ro console=tty0 console=ttyS0,115200n8 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0 selinux=1 security=selinux quie
Reference: https://access.redhat.com/articles/3166931
Please provide the package NVR for which bug is seen:
RHEL-9.4.0_HVM_BETA-20240411-x86_64-30-Access2-GP3
How reproducible:
Steps to reproduce
- Launch a RHEL AMI on aws
- Check the console output during boot.
Expected results
More information printed when console connected.
Actual results
Few messages printed now.
- links to
-
RHBA-2024:128655 osbuild bug fix and enhancement update