Bug 883461

Summary: FC18: Kickstart installation is not possible.
Product: [Fedora] Fedora Reporter: IBM Bug Proxy <bugproxy>
Component: pykickstartAssignee: Chris Lumens <clumens>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: bcl, clumens, g.kaviyarasu, jkachuck, jonathan, jstodola, sbueno, vanmeeuwen+fedora, wgomerin
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-22 18:56:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screen shot for OBSERVATION 1, parse error in ks file
none
Screen shot for OBSERVATION 2, no IP address found
none
The kickstart file none

Description IBM Bug Proxy 2012-12-04 16:32:43 UTC 
Once the manual installation is done a kickstart file "anaconda-ks.cfg" gets stored in the /root directory. If we take this kickstart file and point to it in the ".parms" file, and restart the manual installation, there are certain errors thrown by the installer. Please refer to the screen-shots.

These are the following two errors that we find:

1. parse-kickstart ERROR: The following problem occurred on line 23 of the kickstart file:
unknown command: --type=lvm
2. No IP addresses found, cannot continue installation
Comment 1 IBM Bug Proxy 2012-12-04 16:33:06 UTC 
Created attachment 657633 [details]
Screen shot for OBSERVATION 1, parse error in ks file
Comment 2 IBM Bug Proxy 2012-12-04 16:33:27 UTC 
Created attachment 657634 [details]
Screen shot for OBSERVATION 2, no IP address found
Comment 3 IBM Bug Proxy 2012-12-04 16:33:46 UTC 
Created attachment 657635 [details]
The kickstart file
Comment 4 IBM Bug Proxy 2012-12-05 09:31:08 UTC 
------- Comment From manibajp.com 2012-12-05 09:27 EDT-------
(In reply to comment #10)
> Could you also include what release of Fedora 18 you're installing?

I was trying this on the release:

http://s390.koji.fedoraproject.org/tree/test/20121113/s390x/os/

and the same issue can also be observed on the beta release i.e.:

http://s390.koji.fedoraproject.org/tree/test/20121128/s390x/os/
Comment 5 Chris Lumens 2012-12-05 15:18:54 UTC 
Please file a second bug for the second issue.  The first appears to be a pykickstart problem, so I am going to move it to that component.
Comment 6 Chris Lumens 2012-12-07 20:21:02 UTC 
I am unable to reproduce the issue with the bad line in the kickstart file.  Can you think of any choices you made during installation that could have affected this?  Also, can you please try a post-beta tree and see if that fixes this for you?  Thanks.
Comment 7 Jan Stodola 2013-01-25 12:09:24 UTC 
The first issue seems to be the same as bug 888841.
Comment 8 IBM Bug Proxy 2013-02-07 09:21:28 UTC 
------- Comment From onmahaja.com 2013-02-07 09:10 EDT-------
RH, Any progress on this issue ?
Comment 9 IBM Bug Proxy 2013-08-05 17:55:52 UTC 
(Note: fix for the repeated needinfo flags during mirroring was implemented earlier this year; attempt to clear the flags to validate.)
Comment 10 Chris Lumens 2013-08-22 18:56:23 UTC 
If you can reliably reproduce the second problem, please open a new bug against anaconda containing /tmp/anaconda.log and your kickstart file.  Thanks.

*** This bug has been marked as a duplicate of bug 888841 ***