Red Hat Bugzilla – Bug 888841
anaconda-ks.cfg created by anaconda contains unknown commands
Last modified: 2014-01-30 03:33:24 EST
Description of problem:
/root/anaconda-ks.cfg created by anaconda contains an unknown command:
# cat /root/anaconda-ks.cfg
bootloader --location=mbr --boot-drive=sda
See steps to reproduce.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start graphical installation
2. go to "Installation Destination", select all drives and click "Continue"
3. check "I don't need help, let me customize disk partitioning", click "Reclaim space"
4. remove all existing partitions
5. click "Click here to create then automatically."
6. finish partitioning
7. finish the installation and reboot
8. check /root/anaconda-ks.cfg
unknown command in kickstart:
# ksvalidator anaconda-ks.cfg
The following problem occurred on line 24 of the kickstart file:
Unknown command: --type=lvm
Created attachment 666197 [details]
Created attachment 666198 [details]
Created attachment 666199 [details]
Created attachment 666200 [details]
Created attachment 666201 [details]
Created attachment 666202 [details]
I think this is a pykickstart bug, but I've not been able to reproduce it outside of anaconda.
Oh, I see the pykickstart side. There may potentially also be an anaconda part to this, given your step #5.
*** Bug 908592 has been marked as a duplicate of this bug. ***
Bug 929119 prevents from verification of this bug, setting bug dependency accordingly.
[root@localhost ~]# rpm -q pykickstart
[root@localhost ~]# ksvalidator anaconda-ks.cfg
[root@localhost ~]# echo $?
[root@localhost ~]# grep autopart anaconda-ks.cfg
Moving to VERIFIED.
*** Bug 883461 has been marked as a duplicate of this bug. ***
Created attachment 789318 [details]
Screen shot for OBSERVATION 1, parse error in ks file
Created attachment 789319 [details]
Screen shot for OBSERVATION 2, no IP address found
Created attachment 789320 [details]
The kickstart file
(In reply to IBM Bug Proxy from comment #14)
> Created attachment 789319 [details]
> Screen shot for OBSERVATION 2, no IP address found
The last two messages in the screenshot are:
anaconda: Starting installer, one moment...
anaconda: 08:09:02 No IP addresses found, cannot continue installation.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
------- Comment From firstname.lastname@example.org 2014-01-30 08:27 EDT-------
CLOSED WONTFIX from IBM side.