Bug 578284

Summary:	Preupgrade fails with kickstart config file error: add disks to clear section
Product:	[Fedora] Fedora	Reporter:	Matt Moldvan <matt>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	bugzilla, jonathan, jurikolo, kparal, matt, npajkovs, psj, richard, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-14 17:41:44 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:
Bug Depends On:
Bug Blocks:	507681

Description Matt Moldvan 2010-03-30 18:50:18 UTC

Description of problem: After reboot, error is encountered:

Error parsing kickstart config

The following error was found while parsing the kickstart configuration file:

The kickstart configuration file is missing required information that anaconda cannot prompt for.  Please add the following sections and try again:

Disks to clear


Version-Release number of selected component (if applicable):
preupgrade-1.1.4-1.fc12.noarch

How reproducible:

Steps to Reproduce:
1. Run preupgrade, works okay
2. Reboot, encounter error
3.
  
Actual results:
Error message

Expected results:
Upgrade to Fedora 13 from Fedora 12 is successful

Additional info:

Comment 1 Jurijs Kolomijecs 2010-04-02 21:22:42 UTC

Looks like I've created a dublicate: https://bugzilla.redhat.com/show_bug.cgi?id=579114

Same problem.

Comment 2 Chris Lumens 2010-04-05 14:25:16 UTC

*** Bug 579114 has been marked as a duplicate of this bug. ***

Comment 3 Paul Jenner 2010-04-13 18:43:14 UTC

Same problem here attempting preupgrade from Fedora 12 to Fedora 13 beta. Any info I can provide to help?

Comment 4 Kamil Páral 2010-04-14 17:41:44 UTC


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