Bug 219422 - LSPP: Unable to install via kickstart
LSPP: Unable to install via kickstart
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
s390x Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Depends On:
  Show dependency treegraph
Reported: 2006-12-12 19:01 EST by Kylene J Hall
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-15 11:19:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kickstart file (13.65 KB, text/plain)
2006-12-12 19:01 EST, Kylene J Hall
no flags Details
Sample screen shot (633 bytes, text/plain)
2006-12-12 19:02 EST, Kylene J Hall
no flags Details

  None (edit)
Description Kylene J Hall 2006-12-12 19:01:16 EST
Description of problem:
When installing via kickstart I provide the kickstart file via http and the
method info via http in the parm file.  It doesn't seem to find this info and
after the initial network setup in the s390x console I am directed to ssh to the
ip address where I am prompted for the kickstart location and then the install
source.  This time it accepts both of these.  This window then says something
about processing pre-setup scripts.  Back on the z console I am being prompted
for the input in the interactive part of the kickstart script.  However, when I
attempt to answer the questions I am dropped into a shell each time. Multiple
Enters and sometimes throwing in a command such as ps and some more enters
finally bring me to the next question.  On questions that ask y/n I am told the
y or n that I answer is and undefined command.  Thus, I can never actually start
the install b/c the final question is should I actually start the install on
dasda y/n.

Attached is the kickstart file I am using and a snipet of the screen after I
have hit enter multiple times.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Kylene J Hall 2006-12-12 19:01:17 EST
Created attachment 143479 [details]
Kickstart file
Comment 2 Kylene J Hall 2006-12-12 19:02:14 EST
Created attachment 143480 [details]
Sample screen shot
Comment 3 Kylene J Hall 2006-12-14 12:02:46 EST
Any info on this bug?
Comment 5 Jeremy Katz 2006-12-15 11:19:17 EST
Your kickstart config is trying to do things that don't work with the way s390
installs work; /dev/console of s390 is the 3270 but any "input" that happens for
s390 happens on a telnet/ssh login
Comment 6 Archana K. Raghavan 2006-12-15 13:52:21 EST
Bringing in comments from the Issue Tracker:
We will have to make the kickstart script completely non-interactive if we can't
rely on the console. This probably needs to be done anyway for mass
installation, anyway.

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