Impact: dmraid installation is entirely broken in Lucid.
Development branch: For the time being, an upstream patch has been reverted in Maverick: see comment 84 and http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/parted/maverick/annotate/head:/debian/patches/fix-dmraid-regression.patch; however, in future (probably in maverick) we'll fix this differently by switching to the new naming scheme for device-mapper devices, which has more consistent support in upstream code. Such an invasive change would not be appropriate in Lucid - for one, it would require changes to grub2.
TEST CASE: Install Ubuntu on a DM-RAID system using (a) the Ubuntu desktop CD and (b) the Ubuntu server CD. Verify that it succeeds. Note that this requires respins of CD images to test effectively; Colin Watson will arrange for sample daily builds not long after this update is processed.
Regression potential: This change is isolated to code dealing with device-mapper devices, so installations on ordinary hard disks should be unaffected. However, I think it would be a good idea to regression-test installations on LVM and software RAID (as distinct from DM-RAID), as those follow the same code path and may be affected.
Original report follows:
Binary package hint: dmraid
Fresh install of Ubuntu Server 10.04 Beta 2 using Sil 3124 fakeraid controller card. Ubuntu install successfully detects fakeraid set (Raid1) and activates it, but after creating my partition layout using all default options with "Guided Partitioning",when I click finish to apply it, it fails stating it could not create a filesystem.
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
Package: ubiquity 2.2.20
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 18.104.22.168+drm33.2
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare