Red Hat Bugzilla – Bug 456325
cmdline kickstart option not honored
Last modified: 2010-10-22 23:03:49 EDT
+++ This bug was initially created as a clone of Bug #456110 +++
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061017
Description of problem:
My kickstart file includes the 'cmdline' option to select non-ncurses
installation output; I'm streaming this to the serial port (console=ttyS0) to
allow an external system to monitor installation status.
However, anaconda still uses the ncurses interface during installation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Boot a system against a kickstart file similar to the following:
auth --useshadow --enablemd5
clearpart --all --initlabel --drives=sda
langsupport --default=en_US.UTF-8 en_US.UTF-8
# start off on the provisioning network (via DHCP); will be reconfigured later
network --bootproto=dhcp --hostname ems-worker2
rootpw --iscrypted REDACTED
clearpart --all --initlabel
part /boot --size=256
part pv.01 --size=500 --grow
volgroup vg01 pv.01
logvol / --vgname=vg01 --size=1000 --name=root
logvol /usr --vgname=vg01 --size=2048 --name=usr
logvol /var --vgname=vg01 --size=6000 --name=var
logvol /opt --vgname=vg01 --size=4096 --name=opt
anaconda installs the system according to the directives given in the kickstart
file, but uses its ncurses interface to show status
Updates on the ongoing operations taken by anaconda should have been printed to
the console in a non-curses-based (highly parsable) manner.
-- Additional comment from firstname.lastname@example.org on 2008-07-21 12:23 EST --
Also filed at http://bugs.centos.org/view.php?id=3008
-- Additional comment from email@example.com on 2008-07-21 23:39 EST --
This is not a bug in anaconda: text is being chosen over cmdline as cobbler is
adding 'text' to the kernel command line.
There doesn't appear to be a mechanism to prevent this, which I'm taking up with
the Cobbler team; in any event, it's quite certainly not an anaconda issue.
-- Additional comment from firstname.lastname@example.org on 2008-07-22 15:03 EST --
I closed this ticket in error; there is in fact a bug in anaconda head which
prevents cmdline from being respected if X is not being installed on the target.
Attaching patches against RHEL4 and RHEL5.
-- Additional comment from email@example.com on 2008-07-22 15:06 EST --
Created an attachment (id=312386)
rhel4 fix for cmdline being overridden by text when graphical install is
detected as unworkable
-- Additional comment from firstname.lastname@example.org on 2008-07-22 15:07 EST --
Created an attachment (id=312387)
rhel5 fix for cmdline being overridden by text when graphical install is
detected as unworkable
-- Additional comment from email@example.com on 2008-07-22 16:51 EST --
please also add the patch listed at
*** Bug 461230 has been marked as a duplicate of this bug. ***
Steps to reproduce:
1. Start a virtual guest with less than 288MB RAM (200MB, PV Xen guest) *
2. Provide a complete kickstart file which contains 'cmdline' command
3. Proceed with install
4. X can't start (not enough memory, X not on minstg2.img) - anaconda falls
back to curses based text mode instead of going to cmdline mode.
* - in the code GUI_STAGE2_RAM 294912 = 288MB
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
The fix will be available in anaconda 126.96.36.199
Is related bug 499143 also solved with the upcoming anaconda?
*** Bug 499143 has been marked as a duplicate of this bug. ***
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
VERIFIED with 0701.0 tree and the steps to reproduce in comment #2
Confirmed -- cannot reproduce with 5.4 beta.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.