Bug 526223

Summary:	--label kickstart option not written in anaconda-ks.cfg
Product:	[Fedora] Fedora	Reporter:	Alexander Todorov <atodorov>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	anaconda-maint-list, rwilliam, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-13.0-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-10-05 12:46:51 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:

Description Alexander Todorov 2009-09-29 11:05:01 UTC

Description of problem:
When using a kickstart partitioning command which has --label option this option is not present in the resulting anaconda-ks.cfg file.

Version-Release number of selected component (if applicable):
anaconda-12.31-1.fc12.x86_64.rpm
pykickstart-1.63-1.fc12.noarch.rpm

How reproducible:
always

Steps to Reproduce:
1. Install with ks.cfg that has:
part /multi-stage --fstype="ext3" --size=100 --label=MULTISTAGE
2.
3.
  
Actual results:
The resulting anaconda-ks.cfg has:
#part /multi-stage --fstype=ext3 --size=100


Expected results:
#part /multi-stage --fstype=ext3 --size=100 --label=MULTISTAGE


Additional info:

Comment 2 Chris Lumens 2009-10-02 18:14:05 UTC

Sadly, all the anaconda-ks.cfg writing is still done by anaconda.  This is because none of the __str__ methods in storage/ know to write out a --label=.