lvm encryption fails in jaunty

Bug #314168 reported by Dustin Kirkland 
2
Affects Status Importance Assigned to Milestone
partman-crypto (Ubuntu)
Fix Released
High
Colin Watson

Bug Description

Binary package hint: partman-lvm

Trying today's Jaunty server amd64 build, encrypted LVM fails.

I choose:
 Guided - use entire disk and set up encrypted LVM

I select my disk.

I choose "Yes" to the question, "Write changes to the disks and configure LVM."

And it just kicks me back to the "Partition Disks" screen.

:-Dustin

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

/var/log/syslog attached.

:-Dustin

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

/var/log/partman attached.

:-Dustin

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Note that simple guided LVM partitioning works as expected.

:-Dustin

Revision history for this message
Colin Watson (cjwatson) wrote :

Fairly straightforward to fix - we just need to cope with the dm modules being built-in. (I've reproduced the bug and that a crude workaround makes it go away; I'm just looking at something a little more sophisticated that would be suitable for upstream use.)

Changed in partman-crypto:
assignee: nobody → kamion
importance: Undecided → High
milestone: none → jaunty-alpha-3
status: New → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

I'll work around the problems for dm_mod and dm_crypt. Per IRC discussion, Tim is going to avoid the crypto module problems by reverting to building these as modules rather than building them in.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package partman-crypto - 36ubuntu2

---------------
partman-crypto (36ubuntu2) jaunty; urgency=low

  * Handle dm_mod and dm_crypt specially in crypto_load_module, to cope with
    them being built-in (LP: #314168).

 -- Colin Watson <email address hidden> Tue, 06 Jan 2009 15:54:52 +0000

Changed in partman-crypto:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.