precise alternate LVM failed to install: no root file system

[Jean-Baptiste Lallement]

Precise Alternate i386/amd64 20120127.2 LVM

TEST CASE
1. At the partitioning step select: use entire disk and setup LVM
2. Write to disk and accept the amount of VG to use (10G in this case)

RESULT:
Partitioning setup fails with:
No root file system
No root file system is defined

Guided partitioning without LVM works fine.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: debian-installer (not installed)
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Jan 27 16:23:31 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Inspiron N4010
MemoryUsage:
 total used free shared buffers cached
 Mem: 2943228 2725496 217732 0 37732 796032
 -/+ buffers/cache: 1891732 1051496
 Swap: 2928636 215948 2712688
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=d8966312-304d-4504-b854-5ec365ce6e20 ro quiet splash vt.handoff=7
SourcePackage: debian-installer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/19/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 021CN3
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Inspiron N4010
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.

[Colin Watson (cjwatson)]

It's created the LVs but doesn't seem to have told partman about them.

[Colin Watson (cjwatson)]

I'm fairly sure this is a regression due to the changes in parted 2.3-8ubuntu2. I'll consider backing those out but would prefer to try to fix them first.

[Colin Watson (cjwatson)]

OK. There are multiple problems here.

 1) parted has stopped probing DM devices that aren't DM-RAID. partman-base needs it to support this.
 2) partman parses the output of 'multipath -l' to decide whether a device is a multipath device. Foolishly, multipath prints errors to standard output, such as a complaint about dm-multipath not being loaded.
 3) dmraid-udeb depends on multipath-udeb for kpartx. There is no kpartx-udeb.

For 1), I'm going to restore this support; it's part of parted's interface now and shouldn't be broken.

For 2), mostly we avoid this because we only ever install multipath-udeb in code that modprobes dm-multipath, but dmraid-udeb just broke this assumption. Fixing this properly seems fiddly, not least because I can't test that I haven't broken multipath in the process, so I'm inclined to just restore this assumption by creating kpartx-udeb and having dmraid-udeb depend on that.

[Launchpad Janitor (janitor)]

This bug was fixed in the package parted - 2.3-8ubuntu3

---------------
parted (2.3-8ubuntu3) precise; urgency=low

  * Probe non-dmraid device-mapper devices again (LP: #922646).
 -- Colin Watson <email address hidden> Fri, 27 Jan 2012 22:59:12 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu3

---------------
multipath-tools (0.4.9-3ubuntu3) precise; urgency=low

  * Move kpartx from multipath-udeb to a new kpartx-udeb package
    (LP: #922646).
 -- Colin Watson <email address hidden> Fri, 27 Jan 2012 23:04:23 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package dmraid - 1.0.0.rc16-4.1ubuntu6

---------------
dmraid (1.0.0.rc16-4.1ubuntu6) precise; urgency=low

  * Depend on kpartx-udeb rather than multipath-udeb, now that it exists
    (LP: #922646).
 -- Colin Watson <email address hidden> Sat, 28 Jan 2012 11:37:27 +0000