Bug 587665 - Generated anaconda-ks.cfg contains None values in partition keywords
Summary: Generated anaconda-ks.cfg contains None values in partition keywords
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-30 14:05 UTC by James Laska
Modified: 2013-09-02 06:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 15:59:18 UTC
Type: ---

Attachments (Terms of Use)

Description James Laska 2010-04-30 14:05:52 UTC
Description of problem:

Installing a system with the following kickstart commands:

  # System bootloader configuration
  bootloader --location=mbr
  # Partition clearing information
  clearpart --all --initlabel 
  # Disk partitioning information
  part /boot --asprimary --fstype="ext3" --size=500 --label=BOOT
  part swap --fstype="swap" --recommended --label=SWAP
  part /multi-stage --fstype="ext3" --size=100 --label=MULTISTAGE
  part raid.01 --grow --size=2048
  part raid.02 --grow --size=2048
  part raid.03 --grow --size=2048
  part raid.04 --grow --size=2048
  raid / --device=0 --fstype="ext3" --level=RAID5 raid.01 raid.02 raid.03 raid.04

Produces a /root/anaconda-ks.cfg that contains:

  # The following is the partition information you requested
  # Note that any partitions you deleted are not expressed
  # here so unless you clear all partitions first, this is
  # not guaranteed to work
  #clearpart --all --initlabel
  #raid / --fstype=ext3 --level=5 --device=md0 raid.None raid.None raid.None raid.None
  #part /boot --fstype=ext3 --label="BOOT" --asprimary --size=500
  #part raid.None --grow --size=2048
  #part raid.None --grow --size=2048
  #part raid.None --grow --size=2048
  #part raid.None --grow --size=2048
  #part swap --label="SWAP" --grow --maxsize=1472 --size=736
  #part /multi-stage --fstype=ext3 --label="MULTISTAGE" --size=100
  bootloader --location=mbr --driveorder=vda,vdb,vdc,vdd --append="console=ttyS0 rhgb quiet"

Version-Release number of selected component (if applicable):
 * anaconda-13.39
 * pykickstart-1.69-1.fc13

Comment 1 Chris Lumens 2010-04-30 19:27:21 UTC
At the end of installation, before you reboot, can you switch to tty2, press up until you get to the killall command, run that, and attach /tmp/anaconda-tb-* to this bug report?  Thanks.

Comment 2 Bug Zapper 2011-06-02 14:41:06 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-27 15:59:18 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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