Bug 804365

Summary: cryptsetup luksFormat fails "device-mapper: table: 253:0: crypt: unknown target type"
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: cryptsetup-luksAssignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: agk, dwysocha, lvm-team, mbroz, okozina, pjones, prockai, whulbert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-18 10:32:11 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 Richard W.M. Jones 2012-03-18 09:28:51 UTC 
Description of problem:

This just started to happen in Rawhide (as in, it didn't
happen two days ago).  I'm not sure if it's a kernel or
LUKS problem.

# parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s
# cryptsetup -q --key-slot 0 luksFormat /dev/vda1 /tmp/luksykr7fm
[   56.250443] device-mapper: table: 253:0: crypt: unknown target type
[   56.250879] device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl on temporary-cryptsetup-110 failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/vda1.
Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info).
Failed to write to key storage.

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

kernel-3.3.0-0.rc7.git2.1.fc18
cryptsetup-libs-1.4.1-2.fc17
device-mapper-libs-1.02.74-3.fc18.x86_64

How reproducible:

Unknown, at least once.

Steps to Reproduce:

[see above]

Additional info:

Full logs here --
http://koji.fedoraproject.org/koji/taskinfo?taskID=3905286
Comment 1 Milan Broz 2012-03-18 10:32:11 UTC 
Apparently dm-crypt kernel module missing somewhere.

*** This bug has been marked as a duplicate of bug 804345 ***