Bug 557389

Summary: anaconda crashes during setup of LVM partitions
Product: [Fedora] Fedora Reporter: Jos de Kloe <josdekloe>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: hdegoede, jonathan, 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-02-04 23:37:49 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
the anaconda log file
none
the anaconda error log
none
the disk layout before entering the installation procedure none

Description Jos de Kloe 2010-01-21 10:04:16 UTC
Created attachment 385890 [details]
the anaconda log file

Description of problem:

when creating the suggested partition layout, the anaconda installer crashes with the following error:

10:24:15 CRITICAL: anaconda 12.46 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devices.py", line 2030, in _setSize
    raise ValueError("not enough free space in volume group")
  File "/usr/lib/anaconda/storage/partitioning.py", line 1201, in growLVM
    lv.size += grow_amounts[lv.name]
  File "/usr/lib/anaconda/storage/partitioning.py", line 213, in doAutoPartitio
n
    growLVM(anaconda.id.storage)
  File "/usr/lib/anaconda/dispatch.py", line 200, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 123, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 1195, in nextClicked
    self.anaconda.dispatch.gotoNext()
ValueError: not enough free space in volume group


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

version 12.46 from the Fedora 12 i386 install DVD

How reproducible:

happens everytime

Steps to Reproduce:
1. attach external usb dvd-writer to my acer-aspire-one 110AGb netbook (1 GB ram, 16 GB SSD disk)
2. start computer and enter graphical install sequence
3. anaconda starts, and seems to work fine upto the entering of the root password. At the partitioning stage, the bug happens when accepting the presdented defaults and hitting next.
It does not happen when choosing the cusom partitioning layout.

Actual results:

anaconda crashes with a python backtrace as mentioned above.

Expected results:

anaconda should present a reasonable default partitioning

Additional info:

see attached log and error-log files.

Comment 1 Jos de Kloe 2010-01-21 10:05:09 UTC
Created attachment 385891 [details]
the anaconda error log

Comment 2 Hans de Goede 2010-01-25 09:36:08 UTC
Dave,

This is probably a duplicate of something, but you'll know if it is and of what a lot better then me.

Regards,

Hans

Comment 3 David Lehman 2010-01-25 16:30:37 UTC
It looks like you chose "replace existing linux system" in from the automatic partitioning choices. The first (and largest) partition on your disk does not have any formatting that we could identify, so we did not remove it when clearing the "linux" partitions from the disk. If you had chosen "use entire drive" you would have seen the desired result.

Does this sound like what happened? If so, let me know.

If not, please follow this procedure to gather some further information:

 1. switch to tty2 (ctl+alt+f2)
 2. run this:

      parted /dev/sda print > /tmp/sda-layout

 3. scp the file /tmp/sda-layout to another computer
 4. attach that file to this bug report

Thanks.

Comment 4 Jos de Kloe 2010-01-28 15:17:25 UTC
Hi,

Thanks for your responses.
Yes I did choose "replace existing linux system" since this was the default presented by anaconda.
 
The existing partitions where a 15.1 GB ext2 partition and a 1 GB swap partition. The layout from the suggested parted tool is attached as aa1_parted_sda_layout.txt and seems very clear to me, so I don't understand why anaconda finds it difficult to recognise these as linux partitions.
Then, even if it sees partitions with an unknown type, it should not throw a python error, but catch it and give a proper warning to the user.

The error does not occur if I choose "Use entire drive" or "Create custom layout".

The option "Use free space" clearly doesn't work since there is no unpartitioned space on the disk. This is correctly catched with the error "Could not find enough free space for automatic partitioning..."

The option "Shrink current system" also seems not responding correct to me since it responds with the error "No partitions are available to resize...". This seems the same problem, i.e. not recognising the already existing disk layout.

I hope this helps. If you need any additional info just let me know.

Best regards,

Jos de Kloe

Comment 5 Jos de Kloe 2010-01-28 15:19:04 UTC
Created attachment 387352 [details]
the disk layout before entering the installation procedure

Comment 6 David Lehman 2010-01-28 15:59:21 UTC
The problem of traceback instead of error handling is bug 533797, which will be fixed in Fedora 13 (and is already fixed in rawhide).

The reason we did not identify sda1 as a linux partition is that udev (blkid) did not identify it as having any filesystem on it at all. I would suggest that you file a separate bug report against blkid (the package is called util-linux-ng) for its inability to identify your ext2 filesystem.

Comment 7 Jos de Kloe 2010-01-30 15:29:41 UTC
Thanks for your answer.
I filed a bug on util-linux-ng then, referring to this one.
See: https://bugzilla.redhat.com/show_bug.cgi?id=560244

Comment 8 David Lehman 2010-02-04 23:37:49 UTC
The anaconda part of this bug has already been addressed, so I am indicating as much.

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