Description of problem: Unlocking LUKS encrypted volume in anaconda installer The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 345, in _addDevice raise ValueError("device is already in tree") File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 961, in addUdevDiskDevice self._addDevice(device) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1079, in addUdevDevice device = self.addUdevDiskDevice(info) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1894, in _populate self.addUdevDevice(dev) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1842, in populate self._populate() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2513, in on_unlock_clicked self.__storage.devicetree.populate() ValueError: device is already in tree Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.11 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 679933 [details] File: anaconda-tb
Created attachment 679934 [details] File: anaconda.log
Created attachment 679935 [details] File: environ
Created attachment 679936 [details] File: ifcfg.log
Created attachment 679937 [details] File: packaging.log
Created attachment 679938 [details] File: program.log
Created attachment 679939 [details] File: storage.log
Created attachment 679940 [details] File: syslog
I am trying to install on top of an existing F17 install. I have one drive with / and /boot partitions. Another drive is an Intel take RAID. On the fake RAID there is an encrypted partition. After I had enter5ed the password for the encrypted partition (after selecting it from the lower tab on the left in manbual partition define) Anaconda bombed out Package: anaconda-18.37.11-1.fc18.x86_64 OS Release: Fedora release 18
(In reply to comment #9) > I am trying to install on top of an existing F17 install. I have one drive > with / and /boot partitions. Another drive is an Intel take RAID. On the > fake RAID there is an encrypted partition. After I had enter5ed the password > for the encrypted partition (after selecting it from the lower tab on the > left in manbual partition define) Anaconda bombed out > > Package: anaconda-18.37.11-1.fc18.x86_64 > OS Release: Fedora release 18 Update: This defintely happens after the encrypted partition is made ready, i.e. after the anaconda crash I can find the encrypted partition ready for use in /dev/mapper as a disk partition (the bug is only triggered if the passphrase is correct). In this case the encrypted partition was part of the existing installation from which I was reusing the partitions, i.e. it exists in /etc/crypttab on the disk partition being reused for root in the new install and it's a normal usable encrypted partition.
Update 2: Partial workaround: Make brand new excrypted volume and restore contents from the old one after install. In other words, by using a partition (well, logical volume) which had not previous hosted an encrypted volume, I was able to make anaconda define an encrypted volume which uses LUKS.
I'm trying to upgrade to F18 by reinstalling because FedUp just hangs on RAID/LVM/etc on every boot and never finishes. The PC has a imsm raid controller and is configured to use RAID1, the old F17 system is installed on a single encrypted volume containing my root and my home partition, this was created by F16. I wish to preserve my home partition, so I've entered Manual Partition (after figuring out the "reclaim space"-button meant open manual partioning). Every time I enter the passphrase for the encrypted volume this error appears. The computer is a Dell Studio XPS 435mt Package: anaconda-18.37.11 OS Release: Fedora release 18
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.