Description of problem: Plymouth used to only prompt for a passphrase once, and attempt to use that for all subsequent encrypted devices. As of F-14-TC1, it appears that plymouth prompts for a passphrase for each encrypted device. This is specific to serial console booting. Version-Release number of selected component (if applicable): plymouth-0.8.4-0.20100823.4.fc14 Steps to Reproduce: 1. Combine the following two tests * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_serial_console * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(encrypted)_install Actual results: Prompted for a passphrase for each of the encrypted devices (tested 2 and 4) Expected results: Prompted only once, regardless of the number of encrypted devices (assuming the same passphrase is used for all devices) Additional info:
plymouth-0.8.4-0.20100823.5.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/plymouth-0.8.4-0.20100823.5.fc14
plymouth-0.8.4-0.20100823.5.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update plymouth'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/plymouth-0.8.4-0.20100823.5.fc14
Moving this back to ASSIGNED. I don't believe this is resolved with plymouth-0.8.4-0.20100823.5.fc14. Discussed with Ray on IRC, and it appears an additional patch may need to be backported into F-14. 10:54:33 jlaska: halfline: I attempted to gather plymouth:debug information to post into the issue, but that just seems to hang on boot (might be sending output elsewhere, dunno) 10:55:09 halfline: jlaska: means plymouth is crashing 10:55:41 halfline: jlaska: if you run wth plymouth:debug and plymouth crashes then it will pause() so you can attach with gdb. should probably only do that if the root fs is mounted i guess... 10:56:17 halfline: jlaska: and just to be sure, you rebuilt the initrd after updating? 10:56:27 * jlaska did a fresh install with 'updates-testing' enabled 10:56:53 jlaska: halfline: so the initrd should have only been created using the latest plymouth 10:57:10 halfline: jlaska: there's some output before it hangs right? 10:57:13 halfline: can you post that output? 10:57:39 jlaska: halfline: http://fpaste.org/9Vym/ 10:59:44 halfline: jlaska: sigh, the plymouth in f14 is older than i thought
Tested plymouth-0.8.4-0.20100823.6.fc14 (http://koji.fedoraproject.org/koji/buildinfo?buildID=200648) # rpm -q plymouth plymouth-0.8.4-0.20100823.6.fc14.x86_64 # /usr/libexec/plymouth/plymouth-update-initrd # reboot ... Password for /dev/sdb1 (luks-2b6...):********* ^^^ only prompted one time. The same passphrase was used for remaining encrypted devices. Moving back to MODIFIED, pending updated bodhi that contains plymouth-0.8.4-0.20100823.6.fc14
Easy workaround, enter the passphrase for each time prompted. However, I'd like to request including this fix in F-14 as it's tested, and sufficiently annoying for folks doing serial-console installations that include encrypted partitions (virt).
plymouth-0.8.4-0.20100823.6.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update plymouth'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/plymouth-0.8.4-0.20100823.6.fc14
plymouth-0.8.4-0.20100823.6.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.