Bug 578284 - Preupgrade fails with kickstart config file error: add disks to clear section
Summary: Preupgrade fails with kickstart config file error: add disks to clear section
Keywords:
Status: CLOSED DUPLICATE of bug 575400
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 579114 (view as bug list)
Depends On:
Blocks: F13Blocker, F13FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2010-03-30 18:50 UTC by Matt Moldvan
Modified: 2010-04-14 17:41 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-14 17:41:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.