Bug 1036324

Summary: Failed to go through passphrase entering for encrypted volume at boot on kernel 3.11.9-200
Product: [Fedora] Fedora Reporter: Danil Kolobaev <joesatch>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-04 03:30:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
yum.log output for the timeframe between installed 3.11.7 to the time updated to 3.11.9 none

Description Danil Kolobaev 2013-12-01 00:32:43 UTC 
Description of problem:
Failed to go through passphrase entering for encrypted volume on kernel 3.11.9-200.

Version-Release number of selected component (if applicable):
kernel 3.11.9-200

How reproducible:
100%

Steps to Reproduce:
1. Boot the encrypted volume with kernel 3.11.9-200

Actual results:
Continuous reappearance of:
"Please enter passphrase for disk <> (luks-<>)!:"

After several attempts there is:

[FAILED] Failed to start Cryptography Setup for luks-<>.
See 'systemctl status systemd-cryptsetup@luks<>.service' for details
...

I tried the abovementioned command, but there was:

   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

Expected results:
System boots

Additional info:
The only way to go through the passphrase entering is to use the previous kernel 3.11.7-200. With it everything went fine.
Comment 1 Josh Boyer 2013-12-02 14:30:12 UTC 
This sounds like something in the initramfs changed and isn't working properly, not the kernel itself.  Can you attach the yum.log output for the timeframe between when you installed 3.11.7 to the time you updated 3.11.9?
Comment 2 Danil Kolobaev 2013-12-02 19:30:33 UTC 
Created attachment 831751 [details]
yum.log output for the timeframe between installed 3.11.7 to the time updated to 3.11.9
Comment 3 Justin M. Forbes 2014-01-03 22:06:42 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 4 Danil Kolobaev 2014-01-04 03:30:20 UTC 
I'm closing this bug as it doesn't occur at Fedora 20. Thank you.