Bug 726740

Summary:	Kernel 3.1.0-0.rc0.git9.1.fc17 won't unlock encrypted drive
Product:	[Fedora] Fedora	Reporter:	Tom <thomasbelvin>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	aquini, gansalmon, itamar, jonathan, jwboyer, 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:	2011-07-30 03:03:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tom 2011-07-29 16:38:57 UTC

Description of problem:
Kernel 3.1.0-0.rc0.git9.1.fc17 won't unlock encrypted hard drive, but previous kernel 3.0.0-1.fc16 does.

Version-Release number of selected component (if applicable):
Kernel 3.1.0-0.rc0.git9.1.fc17 

How reproducible:
Everytime

Steps to Reproduce:
1.Updated kernel and can no longer boot with new kernel.
2.
3.
  
Actual results:
This is the error I get:
device mapper: reload ioctl failed: Invalid argument
Failed to setup dm_crypt key mapping for device /dev/sda2
check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Failed to read from key storage

Expected results:
Still unlock old encryption

Additional info:

Comment 1 Josh Boyer 2011-07-29 18:32:36 UTC

This is probably because we messed up some of the pre-RC release handling.  Could you try this build when it completes?

http://koji.fedoraproject.org/koji/buildinfo?buildID=256250

Comment 2 Tom 2011-07-30 02:16:52 UTC

That got it, thanks.

Comment 3 Josh Boyer 2011-07-30 03:03:26 UTC

Thanks for testing!