Description of problem: Fedora 22 Beta TC7, reused existing LUKS standard partition for root. Version-Release number of selected component: anaconda-core-22.20.8-1.fc22.x86_64 The following was filed automatically by anaconda: anaconda 22.20.8-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/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 244, 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-WS-x86_64-22_B-T7 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 elevator=deadline executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 other involved packages: python-blivet-1.0.6-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 product: Fedora release: Fedora release 22 (Twenty Two) type: anaconda version: 22
Created attachment 1010927 [details] File: anaconda-tb
Created attachment 1010928 [details] File: anaconda.log
Created attachment 1010929 [details] File: environ
Created attachment 1010930 [details] File: journalctl
Created attachment 1010931 [details] File: lsblk_output
Created attachment 1010932 [details] File: nmcli_dev_list
Created attachment 1010933 [details] File: os_info
Created attachment 1010934 [details] File: program.log
Created attachment 1010935 [details] File: storage.log
Created attachment 1010936 [details] File: ifcfg.log
Proposed as a Blocker for 22-beta by Fedora user chrismurphy using the blocker tracking app because: "When using the custom partitioning flow, the installer must be able to:Encrypt newly-created storage volumes" 1. Installed TC6 with standard partitions, one XFS /boot, one LUKS encrypted /. 2. Boot TC7, used existing /boot checking reformat, used existing / checking reformat. So it's a new fs volume, but the installer used the existing LUKS volume (UUID remains the same). Open question per criterion whether "reuse existing LUKS with new volume" applies to beta or final, but the installer shouldn't crash.
Bug 1200749 sounds identical, but involves LVM.
Discussed at 2015-04-06 blocker review meeting: https://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-06/f22-blocker-review.2015-04-06-16.00.log.txt . Accepted as a Final blocker and Beta freeze exception: we decided this is a conditional violation of Beta criterion "When using the custom partitioning flow, the installer must be able to: ... Assign mount points to existing storage volumes" in the case the existing volume is encrypted, but that it was most suitable as a Final blocker. We'll take a fix for Beta if anaconda team is happy it's safe.
A fix for this is being tracked as part of the fixes for the bug #1210254.
Another user experienced a similar problem: tried to use existing LUKS encrypted / and /home partitions for installation, didn't change passphrase cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22_B-3 ro rd.live.image quiet rhgb 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
*** Bug 1214415 has been marked as a duplicate of this bug. ***
anaconda-22.20.10-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.10-1.fc22
Another user experienced a similar problem: Use the existing luks encrypted partitions as root/swap. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 initrd=/isolinux/initrd0.img root=live:UUID=701A-C410 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
Package libblockdev-0.11-1.fc22, python-blivet-1.0.8-1.fc22, anaconda-22.20.10-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libblockdev-0.11-1.fc22 python-blivet-1.0.8-1.fc22 anaconda-22.20.10-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6866/libblockdev-0.11-1.fc22,python-blivet-1.0.8-1.fc22,anaconda-22.20.10-1.fc22 then log in and leave karma (feedback).
libblockdev-0.11-1.fc22, python-blivet-1.0.8-1.fc22, anaconda-22.20.10-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Another user experienced a similar problem: Attempted to Install Fedora 22 Beat on an Existing Fedora 21 Installation. LUKS is giving an error during the installation start. Partitioning Scheme: To be reformated (No Encryption Applied) UEFI -> /boot/efi VFAT Boot -> /boot EXT4 LUKS to be reformated Root -> / EXT4 with LUKS Home -> /home with LUKS Existing LUKS to be mounted Local File Storage -> /opt/lfsvr EXT4 cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22_B-3 ro rd.live.image quiet rhgb 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
Another user experienced a similar problem: I'm tryiing to install fedora 22 into an existing btrfs volume that is already luks encrypted. I can get through the disk setup just fine and the installer decrypts the drive. However, it crashes when I click "begin installation" cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22_B-3 ro rd.live.image quiet rhgb rd.live.check 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
Jason: as you can see, it should be fixed in the Final TCs - you can try Final TC2: https://dl.fedoraproject.org/pub/alt/stage/22_TC2/
*** Bug 1204546 has been marked as a duplicate of this bug. ***
Tested in TC4. Works well. Encrypted lvm scenario is much more smoother now (from UX pov.). Excellent work. Thank You!
(In reply to Šimon Lukašík from comment #25) > Tested in TC4. Works well. > > Encrypted lvm scenario is much more smoother now (from UX pov.). > > Excellent work. Thank You! Nice! Thanks for the confirmation.
Another user experienced a similar problem: installing f22 beta from USB stick as a replacement of f21 i have 2 disks with four partitions > four RAID1 volumes / (encrypted, reformating), /boot (not encrypted, reformating), swap (encrypted, reformating), /home (encrypted, keeping data) 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
Another user experienced a similar problem: Hello, I'm attepting to install Fedora 22 beta, but it fails. I want to install the new Fedora replacing the old (F20), but I want to keep my home folder as it is. I have dropedd and recreated the root, swap and boot partiotions one by one and then assigned the original home partion to the /home mount point. I've had my disk already encrypted and I was going to do again. The installer was able to unlock it, but it seems it droped the setting or just the next phase didn't have this setup - not sure how it's organized. Also, tried to unlock in file manager and then just after that perform the installation. I still had to unlock separately and it end up having the sme exception. The error comes when I start the actual installation, I guess when it tries to unlock the disk prior to alter the file system. Thanks for your help. Hope this won't be the same on the next Tuesday :) Regards, Zsolt Harsing 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
Follow-up: It actually deleted the partitions I meant to re-create.
Another user experienced a similar problem: After selecting to wipe my entire drive Anaconda proceeds to the next step where I can create a user and set the root password. It freezes on setting up installtion environment and then tells me a problem occured and closes. 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-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: LUKSError: luks device not configured release: Fedora release 22 (Twenty Two) version: 22
Another user experienced a similar problem: I am trying to do an install (not an upgrade) of a Fedora 20 laptop to Fedora 22 Workstation. I have an ext4 /boot partition (sda1) and an LUKS encrypted partition (sda2) in which all the logical volumes (LVs) for my F20 install reside. I would like to reuse this partition scheme (including the LVs) especially since /home is one of the LVs within the LUKS-encrypted sda2. Unfortunately, the installer has issues with this installation setup. Installation attempt number 1: - select the correct drive, check 'manual partition', DID NOT check the 'encrypt partition' When presented with partition screen, only sda1 and sda2 partitions were shown. The LUKS encrypted sda2 was not unlocked and the existing LVs were not presented. (Expected behavior, BTW). I clicked on sda2, was given a passphrase dialog, and entered the correct passphrase. The LVs **STILL** did not show up. I had to "rescan disks" in order for the unlocked LVs to appear. [Bug #1 IMHO] I walk through all the LVs to map them to the correct mount points, all except /home were set to be formatted to ext4. I set up sda1 to /boot, formatted to ext4 and not encrypted. I accept ack all the warnings and changes. I proceed with the installation. Installation fails with the information hopefully reported in this submission. PLEASE NOTE: I did attempt a second installation method where on the "install destination" screen I checked the "encrypt system" box. I was prompted for a passphrase (entered the original passphrase). However, the behavior was exactly as described above. The python exception output was slightly different at the beginning (paraphrased "luks encryption already present"). So, the installer clearly does not work with encrypted partition schemes created by the installer from previous Fedora releases. The F20 install was conducted in similar fashion as above but did not have any issue with prior encrypted partitions. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat rw rd.live.image rd.live.overlay=LABEL=LIVE quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: LUKSError: luks device not configured release: Fedora release 22 (Twenty Two) version: 22
(In reply to Tim Miller from comment #31) > Another user experienced a similar problem: > > I am trying to do an install (not an upgrade) of a Fedora 20 laptop to > Fedora 22 Workstation. Please note: I am not using a Beta version of Fedora 22. I just downloaded the ISO last night and this problem seems to still exist.
Another user experienced a similar problem: Fedora 22 netinstall does not support full disk (LVM PV level) encryption. As a result, when trying to install it over a functional full-disk encrypted Fedora 21, it destroys /boot then crashes, rendering the system unusable. Apparently the luks tools are missing in this version of the installer. Everything worked fine with Fedora 20 and Fedora 21 installers in the exact same situation, this is a regression introduced in Fedora 22. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=linux_install/f22.x86_64/vmlinuz initrd=linux_install/f22.x86_64/initrd.img inst.stage2=http://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/x86_64/os/ ip=dhcp dnf.rpm.log: Aug 11 09:03:40 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 package: anaconda-22.20.13-1 product: Fedora reason: LUKSError: luks device not configured release: Cannot get release name. version: 22
Another user experienced a similar problem: The latest respins (F22-20150806) are also affected by this defect. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.1.3-201.fc22.x86_64 other involved packages: python-libs-2.7.10-4.fc22.x86_64, python-blivet-1.0.10-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: LUKSError: luks device not configured release: Fedora release 22 (Twenty Two) version: 22