Bug 503100

Summary: storage related anaconda backtraces
Product: [Fedora] Fedora Reporter: Sertaç Ö. Yıldız <sertacyildiz>
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, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-28 21:12:11 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
RuntimeError: Returning partitions to state prior to edit failed
none
ValueError: Cannot remove extended partition sda4. Logical partitions present.
none
PartitionException: Attempting to remove an extended partition that still contains logical partitions none

Description Sertaç Ö. Yıldız 2009-05-28 20:51:50 UTC
Created attachment 345838 [details]
RuntimeError: Returning partitions to state prior to edit failed

Backtraces are from a yum updated f11-preview live usb installation.
(anaconda version 11.5.0.54-1.fc11)

All were related to removing the already existing partitions, so didn't create separate reports.

Comment 1 Sertaç Ö. Yıldız 2009-05-28 20:53:28 UTC
Created attachment 345839 [details]
ValueError: Cannot remove extended partition sda4.  Logical partitions present.

Comment 2 Sertaç Ö. Yıldız 2009-05-28 20:54:56 UTC
Created attachment 345840 [details]
PartitionException: Attempting to remove an extended partition that still contains logical partitions

Comment 3 Chris Lumens 2009-05-28 21:12:11 UTC
All of these are duplicates of existing bug reports.  The first is 502092 and the second two are 500808.  In general, please file one bug per bug report for ease of tracking.  Thanks.

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