Bug 854813 - [Regression] No console for RHEL 5 after installation.
[Regression] No console for RHEL 5 after installation.
Product: Fedora
Classification: Fedora
Component: cobbler (Show other bugs)
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Bill Peck
: Regression
Depends On:
  Show dependency treegraph
Reported: 2012-09-06 00:07 EDT by Gris Ge
Modified: 2012-09-13 10:56 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-09-13 10:56:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gris Ge 2012-09-06 00:07:40 EDT
Description of problem:

    1. We have this kind of line 'console=ttyS1,115200' in
       'Kernel Options' to get console during installation for all
    2. In RHEL 6, anaconda or cobbler generated kickstat fill will copy
       that line to boot kernel, so we get console after installation.
    3. In the good old time, RHEL 5 do the same as RHEL 6.
    4. Now, RHEL 5 got no console after install:

Version-Release number of selected component (if applicable):
current Red Hat beaker production version.

How reproducible:

Steps to Reproduce:
1. Just clone https://beaker.engineering.redhat.com/jobs/288539
Actual results:
No 'console=xxx' line in post kernel option. Which cause no console after installation.

Expected results:
'console=xxx' automatically added to post kernel option.

Additional info:
Regression. I never got this problem when I test RHEL 5.8.

Workaround: copy 'console=xxx' line to 'Kernel Options Post' for RHEL 5 only in beaker web gui.
Comment 1 Dan Callaghan 2012-09-06 01:04:13 EDT
Are you sure this isn't a regression in Anaconda? Beaker has never done anything special to set the console= kernel option after install.
Comment 2 Bill Peck 2012-09-06 09:55:54 EDT
I notice your job has kernel_options_post="kmemleak=on" which makes the following change in the kickstart:

bootloader --location=mbr --append="kmemleak=on"

The install does progress with serial console but I wonder if anaconda fails to pass that along if any append line is requested on the bootloader.

Ultimately I think this is a bug in anaconda but this would help narrow down the issue.

Note You need to log in before you can comment on or make changes to this bug.