Description of problem: Was trying to create encrypted LVM-on-RAID installation. Version-Release number of selected component: anaconda-20.25.14-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.14-1 exception report Traceback (most recent call first): File "/tmp/updates/blivet/devicelibs/crypto.py", line 98, in luks_format raise CryptoError("luks_format failed for '%s'" % device) File "/tmp/updates/blivet/formats/luks.py", line 196, in create key_size=self.key_size) File "/tmp/updates/blivet/deviceaction.py", line 473, in execute options=self.device.formatArgs) File "/tmp/updates/blivet/devicetree.py", line 239, in processActions action.execute() File "/tmp/updates/blivet/__init__.py", line 308, in doIt self.devicetree.processActions() File "/tmp/updates/blivet/__init__.py", line 167, in turnOnFilesystems storage.doIt() File "/tmp/updates/pyanaconda/install.py", line 142, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/tmp/updates/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) CryptoError: luks_format failed for '/dev/md/00' Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-KDE-x86_64-20-TC5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-300.fc20.x86_64 other involved packages: python-libs-2.7.5-9.fc20.x86_64 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 835489 [details] File: anaconda-tb
Created attachment 835490 [details] File: anaconda.log
Created attachment 835491 [details] File: environ
Created attachment 835492 [details] File: journalctl
Created attachment 835493 [details] File: lsblk_output
Created attachment 835494 [details] File: nmcli_dev_list
Created attachment 835495 [details] File: os_info
Created attachment 835496 [details] File: program.log
Created attachment 835497 [details] File: storage.log
Created attachment 835498 [details] File: ifcfg.log
Proposed as a Blocker for 20-final by Fedora user atorkhov using the blocker tracking app because: The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.
Couldn't reproduce on a quick try. TC5 desktop live install in a VM, two 15GB disks. Installation Options, set LUKS and encryption, went to custom part. Wiped all existing partitions. Created 500MB /boot, 12GB / , set LVM container to RAID-1, created 2GB swap . completed configuration and started install, partitioning succeeded, no errors, no crash.
Got this crash submitted in bug 1021507 comment 33 while trying to reproduce.
I was able to make it crash if I checked and immediately unchecked the 'Encrypt' checkbox inside the VG's properties (when setting RAID-1). The LVs have their own Encrypt checkboxes, which are checked by default if you set 'Encrypt my data' on installation options prior to entering custom partitioning. Not sure if it was the same crash as Alexey's, I'll try and reproduce again later.
Looks like I hit something different from Alexey's; it showed up as https://bugzilla.redhat.com/show_bug.cgi?id=1040716 . It seems reproducible with a precise set of steps, trying to pin it down now.
so I don't know precisely what alexey did, but from what I've done with trying encrypted-LVM-on-RAID installs in various ways all afternoon, I'd say it's working well enough to ship; I hit a couple of issues, but it's certainly possible to get an encrypted-LVM-on-soft-RAID install that works. At the moment I'm -1 blocker. If alexey can provide specific reproduction steps for the crasher he hit, it'd help evaluate it.
My steps as described in bug 1021507 comment 33 were like to: 1. Go to installation destination. Select default (LVM, no encryption). 2. Go to custom partitioning. Auto-create partitions 3. Select /, press modify on volume group, check encrypt there. Seems like checking "encrypt" button on volume group is problematic somehow.
Just tried that with RC1 desktop live, worked fine.
Works fine with RC1 too.
If this works with RC1, I'm closing this as fixed.