Description of problem: http://postimg.org/image/95gidtk1p/ http://postimg.org/image/80mg8fxkt/ http://postimg.org/image/fun1tu5dp/ It happens when given that problem you unckeck the "encrypt" checkbox. Happens every time Version-Release number of selected component: anaconda-core-22.20.6-1.fc22.x86_64 The following was filed automatically by anaconda: anaconda 22.20.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/luks.py", line 179, in setup raise LUKSError("luks device not configured") File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 557, in setupParents _format.setup() File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 414, in _preSetup self.setupParents(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 425, in setup if not self._preSetup(orig=orig): File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 549, in setupParents parent.setup(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 414, in _preSetup self.setupParents(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/lvm.py", line 197, in _preSetup return StorageDevice._preSetup(self, orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 425, in setup if not self._preSetup(orig=orig): File "/usr/lib/python2.7/site-packages/blivet/devices/device.py", line 202, in setupParents parent.setup(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/lvm.py", line 623, in setupParents Device.setupParents(self, orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 414, in _preSetup self.setupParents(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 425, in setup if not self._preSetup(orig=orig): File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 661, in execute self.device.setup(orig=True) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 361, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 162, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1058, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 196, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 238, in run threading.Thread.run(self, *args, **kwargs) LUKSError: luks device not configured Additional info: cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-KDE-x86_64-22_B-T4 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc3.git0.1.fc22.x86_64 other involved packages: python-blivet-1.0.5-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 product: Fedora" release: Fedora release 22 (Twenty Two) type: anaconda version: Fedora
Created attachment 1005107 [details] File: anaconda-tb
Created attachment 1005108 [details] File: anaconda.log
Created attachment 1005109 [details] File: environ
Created attachment 1005110 [details] File: journalctl
Created attachment 1005111 [details] File: lsblk_output
Created attachment 1005112 [details] File: nmcli_dev_list
Created attachment 1005113 [details] File: os_info
Created attachment 1005114 [details] File: program.log
Created attachment 1005115 [details] File: storage.log
Created attachment 1005116 [details] File: ifcfg.log
*** This bug has been marked as a duplicate of bug 1198870 ***
Some more details from #fedora-blocker-review description: <Corey84> adamw, create a cryptsetup luksFormat PV <Corey84> add a few LVs inside that <adamw> OK <Corey84> then attempt to reformat fs and mount as usual it attempts to encrypt the LVs ("tombing" ) them which blivet seems ill equipped to handle or throws a FormatCreate error (as it can't poll the cryptsetup params)
Discussed at 2015-03-23 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-23/f22-blocker-review.2015-03-23-16.02.log.txt . There definitely seem to be some issues around the re-use of existing LVM layouts that are encrypted in some way, but we agreed we didn't quite have a clear enough explanation of the details of the various issues to be able to determine blocker status. We asked Corey and Ivan to clearly document the various issues separately and nominate the appropriate ones as blockers, and we'll come back to them next time. The other bug that was mentioned in this context was https://bugzilla.redhat.com/show_bug.cgi?id=1198870 .
Steps to reproduce: 1. Create lvm inside luks with some partitions: <code> # create one partition for /boot, the rest into another partition fdisk /dev/sda cryptsetup luksFormat /dev/sda2 cryptsetup luksOpen /dev/sda2 cryptvolume pvcreate /dev/mapper/cryptvolume vgcreate linux /dev/mapper/cryptovolume lvcreate -n root -L <anysize> linux lvcreate -n home -L <anysize> linux # and so on... reboot </code> 2. Enter installer 3. Unlock /dev/sda2 # For crash 4. Set linux-root as /, reformat and uncheck the "encrypt" box 5. Set linux-home as /home, reformat and uncheck the "encrypt" box # and so on... 6. Click "Done". 7. Start installing # For luks inside lvm inside luks dont uncheck the "encrypt" box
Created attachment 1005547 [details] Screenshots from reproduction
RE: Comment 14 errata: # For luks the LVs inside are not "tombed" aka encrypted only the PV or VG are luks'd
Another user experienced a similar problem: * existing FC19 install * trying to install FC22 to LV in fedora VG, which was previously created (in FC19) * I've unlocked the entries in the installation and even though got asked for passphrase (something wrong here too!) * setup root on root_fc21 and add /boot to mountpoints * click install * error cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22_B-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 other involved packages: python-blivet-1.0.7-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 package: anaconda-core-22.20.9-1.fc22.x86_64 packaging.log: product: Fedora reason: LUKSError: luks device not configured release: Fedora release 22 (Twenty Two) version: 22
Jaroslav: sorry, I don't quite understand what you mean by "I've unlocked the entries in the installation and even though got asked for passphrase (something wrong here too!)". Was the existing F19 install encrypted? In the 'standard' way, by the installer? What exactly did you do in the F22 installer? Thanks!
Another user experienced a similar problem: Install with custom partitioning, using a LUKS encrypted device hosting LVM volumes. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22_B-x86_64 quiet hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 package: anaconda-22.20.9-1 product: Fedora reason: LUKSError: luks device not configured release: Cannot get release name. version: 22
I mean that I unlocked it in the installation, where you set up the partitioning. Without unlocking it it's a big Unknown, then you fill in the password there and click "Unlock", it gets decrypted and LVM volumes from the encrypted part are available. After this was done, I clicked Done and was asked for passphrase once again. Does it make more sense now? :)
Another user experienced a similar problem: Custom partitioning (manual made). one encrypted PV. I had to insert my password twice. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:UUID=8955-6DA0 rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 other involved packages: python-blivet-1.0.7-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 package: anaconda-core-22.20.9-1.fc22.x86_64 packaging.log: product: Fedora reason: LUKSError: luks device not configured release: Fedora release 22 (Twenty Two) version: 22
Do we have any workarounds for this? Or are the users recommended to install F21 and proceed with fedup?
*** This bug has been marked as a duplicate of bug 1208979 ***
*** Bug 1198870 has been marked as a duplicate of this bug. ***