Created attachment 898214 [details] Kickstart file Description of problem: Kickstart file contains part pv.253002 --encrypted --onpart=sda2 --noformat --passphrase=No_Funny_Characters (above all on one line) but the partition does experience a working "cryptsetup luksOpen /dev/sda2 pv.253002" Version-Release number of selected component (if applicable): Fedora 20 install How reproducible: always Steps to Reproduce: 1.Create luks partition 2.Make decrypted device a PV for LVM 3.Create a Volume Group from the PV 4.Create logical volumes on the Volume Group 5.Attempt kickstart directed install onto existing logical volumes Actual results: After Alt-F2, "dmsetup ls" shows only "live-base" and "live-rw". Expected results: Fedora 20 installed on vg_thyrsuslaptop-lv_root Additional info: In the Alt-F2 shell, "cryptsetup luksOpen /dev/sda2 pv.253002" prompts for the password, and after receiving it creates pv.253002 and triggers activation of the contained volume group and makes the logical volumes available. Regrettably, it appears that anaconda cannot be convinced to recognize the newly available storage. I'm including the actual password I used for test, which I'll be removing from the test partition with "cryptsetup luksRemoveKey" once I get this working; if I've committed some kind of syntax blunder on the kickstart "part" line, let me know.
Created attachment 898215 [details] storage log from kickstart directed install attempt
Created attachment 898216 [details] anaconda.log from install attempt
In the storage.log, why does it say "passphrase = (not set)" when it is set in the kickstart file? In /usr/lib/python2.7/site-packages/blivet/devicelibs/cryptsetup.py the routine luks_open has raise ValueError("luks_format requires passphrase") which should be "luks_open requires passphrase".
I was going to try this: bash-4.2$ diff -c anaconda/usr/lib/python2.7/site-packages/blivet/devicetree.py a/usr/lib/pythons2.7/site-pakcages/blivet/devicetree.py *** anaconda/usr/lib/python2.7/site-packages/blivet/devicetree.py 2014-05-24 19:10:21.972667280 -0400 --- a/usr/lib/pythons2.7/site-pakcages/blivet/devicetree.py 2014-05-27 02:56:30.558959988 -0400 *************** *** 1168,1174 **** luks_device = LUKSDevice(device.format.mapName, parents=[device], ! exists=True) try: luks_device.setup() except (LUKSError, CryptoError, DeviceError) as e: --- 1168,1175 ---- luks_device = LUKSDevice(device.format.mapName, parents=[device], ! exists=True, ! passphrase=device.format.passphrase) try: luks_device.setup() except (LUKSError, CryptoError, DeviceError) as e: ...however, when I put it in in the kernel arguments as updates=http://gold/updates.img I see a new error [ 37.496983] dracut-initqueue[475]: gzip: stdout: Broken pipe (the web server log shows the file having been delivered status 200 to the installing host using agent curl/7.32.0). From within the Alt-F2 environment, I can download it with wget, but cd / gunzip < updates.img | cpio -i cpio: usr/lib/python2.7/site-packages/blivet/devicetree.py not created: newer or same age version exists ...which makes no sense since ls -l --time-style=full-iso usr/lib/python2.7/site-packages/blivet/devicetree.py rw-r--r--. 1 root root 95653 2013-12-11 22:11:08.000000000 +0000 usr/lib/python2.7/site-packages/blivet/devicetree.py gunzip < updates.img | cpio -i -t -v ... -rw-r--r-- 1 4121 4121 95699 May 27 05:56 usr/lib/python2.7/site-packages/blivet/devicetree.py There is no /run/install/updates directory.
Is there a way to restart anaconda from the Alt-F2 window? Plain /sbin/anaconda fails for me complaining pyanaconda.keyboard.InvalidLayoutVariantSpec: 'us,us' is not a valid keyboard layout and variant specification
I believe there is a restart-anaconda script you can run.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.