Bug 495822

Summary: Exception while reinitializing disk
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, pjones, rmaximo, 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: 2009-04-15 13:56:29 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:
Attachments:
Description Flags
Anaconda traceback none

Description Bruno Wolff III 2009-04-15 00:17:03 UTC
Created attachment 339600 [details]
Anaconda traceback

Description of problem:
I wrote over the partition data in order to force anaconda to reinitialize the partitions since there was some partitially valid data from previous failed install attempts that might have been causing problems. However this resulted in an exception.

Version-Release number of selected component (if applicable):
April 14 rawhide boot.iso. The failure happened before networking was set up so it wouldn't have been using the updates.img I had in my local repo.

How reproducible:
So far I have only tried once.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bruno Wolff III 2009-04-15 00:24:23 UTC
Further testing with specifying updates as a kernel parameter seems to prevent the problem, so it's probably already been fixed. But it also might be the third disk had different random data that didn't cause an exception.

Comment 2 Chris Lumens 2009-04-15 13:56:29 UTC

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