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:
"waagent --serialconsole" fails to locate the grub configuration file on rhel7.
rhel6 uses grub, however rhel 7 uses grub2. So this command fails to append the serial console options.
Version-Release number of selected component (if applicable):
WALinuxAgent-2.0.16-1.el7
How reproducible:
Always
Steps to Reproduce:
1. waagent --serialconsole
2. Check the line "GRUB_CMDLINE_LINUX" in /etc/default/grub and the kernel options in /boot/grub2/grub.cfg. Nothing like "console=ttyS0 earlyprintk=ttyS0" is added to these files.
Actual results:
Expected results:
In /etc/default/grub, the options should be appended to the line "GRUB_CMDLINE_LINUX". And run grub2-mkconfig.
Or in /boot/grub2/grub.cfg the options should be appended to the kernel line.
Additional info:
For rhel7,
grubKernelBootOptionsFile = '/etc/default/grub'
grubKernelBootOptionsLine = 'GRUB_CMDLINE_LINUX='
Yes, when we prepare the Azure image, we add "console=ttyS0 earlyprintk=ttyS0" to the grub files manually.
By running command "waagent --serialconsole", it is supposed to do the same thing. It's documented in WALinuxAgent Github:
-serialconsole: Configures GRUB to mark ttyS0 (the first serial port) as
the boot console. This ensures that kernel bootup logs are sent to the
serial port and made available for debugging.
It's more like a nice to have feature, as it doesn't block any function. But I think we could make it fixed in the agent.
(In reply to lizzha from comment #3)
> Yes, when we prepare the Azure image, we add "console=ttyS0
> earlyprintk=ttyS0" to the grub files manually.
>
> By running command "waagent --serialconsole", it is supposed to do the same
> thing. It's documented in WALinuxAgent Github:
> -serialconsole: Configures GRUB to mark ttyS0 (the first serial port) as
> the boot console. This ensures that kernel bootup logs are sent to the
> serial port and made available for debugging.
>
> It's more like a nice to have feature, as it doesn't block any function. But
> I think we could make it fixed in the agent.
Agree, this issue not affect on-demand vm image. Nice to fix it on WALA latest version to make WALA more robust.
Liz
Make sense, thank you for comment.
Wei
Thank you for pointing it out. We will fix this in next version.
Given it's not a blocking bug for your test, can you please move on your test?
(In reply to mingzhan from comment #5)
> Liz
> Make sense, thank you for comment.
> Wei
> Thank you for pointing it out. We will fix this in next version.
> Given it's not a blocking bug for your test, can you please move on your
> test?
Sure, it is not a blocker.