Bug 496660

+++ This bug was initially created as a clone of Bug #496343 +++

The following was filed automatically by anaconda:
anaconda 11.5.0.46 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/packages.py", line 144, in turnOnFilesystems
    except DeviceError as (msg, device):
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 1323, in nextClicked
    self.anaconda.dispatch.gotoNext()
ValueError: need more than 1 value to unpack


--- Additional comment from andreas on 2009-04-17 18:10:21 EDT ---

Created an attachment (id=340102)
Attached traceback automatically from anaconda.

--- Additional comment from andreas on 2009-04-17 18:24:58 EDT ---

Description:

During installation onto a encrypted partition anaconda crashes with the above traceback. I do believe it is rather misleading, as gotoNext() shouldn't have been called.

I do believe the problem is related to a discrepancy between encrypted block devices and real existing partitions.

Steps to reproduce:

1. Take a system with existing partitions and lots of free space at the end of the disk: e.g. sda1 already existing, to be formatted as /boot. sda2 existing NTFS partition, sda3 /boot from another installation, sda4 extended, sda5 lvm from another installation of another linux.
2. Install with default values.
3. Select partitioning scheme "Use free space"
4. Check the Encryption toggle.
5. Check review layout.
6. Delete the newly created /boot partition on sda6 and assign sda1 to be used as the boot partition.
7. Observe that the encrypted pv has correctly changed from sda7 to sda6
8. Edit the lv details. Note that it's supposed to be installed onto crypt-sda7, the former name of the pv.

After the crash, the anaconda logfile shows that createion of crypt sda7 is marked as false.

--- Additional comment from clumens on 2009-04-20 10:25:21 EDT ---

The real error here is hidden from a problem with exception handling, so it's not really easy to tell what's gone wrong.  I've committed a fix to the exception handling part.  After this makes it into a rawhide build, we can look at the real error and work that in a separate report.

--- Additional comment from jlaska on 2009-04-20 10:55:21 EDT ---

Created an attachment (id=340359)
Attached traceback automatically from anaconda.