Bug 218691 - anaconda partitioning crash
Summary: anaconda partitioning crash
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: parted
Version: 6
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-06 20:35 UTC by Stuart MacDonald
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-30 19:00:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stuart MacDonald 2006-12-06 20:35:12 UTC
Description of problem:

During an install, during the partitioning process, I triggered:

Assertion (part->part_list == NULL) at disk.c:1807
In function ped_disk_remove_partition() failed.

In a previous install I had selected "default layout". This time I selected
"custom layout". I deleted all the partitions by selecting the top-most drive
(the LVM in one case, the actual drives in others) and "delete". Then I created
one new partition on my RAID-0 drive that spanned the entire drive. Then I
created a /boot that was 100 MB in size on the primary hd. Then I wanted to
look at the default layout again because I couldn't remember if it had
allocated a swap partition or not. So I hit Back. Then I picked "Remove all
partitions on selected drives and create default layout". Then it crashed.

Version-Release number of selected component (if applicable):

Fedora Core 6.

How reproducible:

I don't have time to try to reproduce it, sorry.

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

Installer crash.

Expected results:

A default layout should have been created. (I had the Review... layout option
checked as well.)

Additional info:

Comment 1 David Cantrell 2007-01-30 19:00:36 UTC
Just tested this scenario with a rawhide tree from 29-Jan-2007 and it doesn't
crash.  Closing this bug.


Note You need to log in before you can comment on or make changes to this bug.