Red Hat Bugzilla – Bug 513951
Anaconda ignores value of RUNKS variable
Last modified: 2010-03-30 04:01:56 EDT
Description of problem:
When RUNKS=0 is set in cmsconffile, anaconda ignores this value and runs noninteractive installation, but Installation Guide writes:
Where value is defined as 1 if you want to run the installation program in noninteractive (kickstart) mode in the 3270 terminal, or 0 otherwise.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. insert RUNKS=0 into cmsconffile
2. start installation
Anaconda is running in noninteractive mode
Anaconda is running in interactive mode
The only way how to run installation in interactive mode is to remove RUNKS variable from cmsconffile.
Starting at line 143 in linuxrc.s390, we have this:
if [ -z "$RUNKS" ]; then
echo $"Connect now to $IPADDR and login as user root to start the installation."
echo $"E.g. using: ssh -X root@$IPADDR"
while : ; do
[ $? = 0 ] || break
That if test should read:
if [ -z "$RUNKS" ] || [ "$RUNKS" = "0" ]; then
Or whatever the valid shell syntax is. The new linuxrc.s390 assumes *any*
value in RUNKS means do a non-interactive install. Oops.
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
Verified with RHEL5.5-Server-20100117.0 and anaconda-188.8.131.52-1.
David's fix from http://git.fedorahosted.org/git/anaconda.git?p=anaconda.git;a=commitdiff;h=c01cbdfd5348bfc1c405fd5ae364e9db9510bd78;hp=7ee506c82f71eb048a473865579dd7febdadb903 is perfect. It automatically takes care of all the other occurrences of testing $RUNKS in linuxrc.
Just for completeness:
(In reply to comment #3)
> Or whatever the valid shell syntax is. The new linuxrc.s390 assumes *any*
> value in RUNKS means do a non-interactive install. Oops.
Which is exactly what the old linuxrc.s390 did, so no change nor regression introduced here. Only when I heard of the same bug for RHEL6, I realized that the install guide has always also said something different:
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.