[Bug 1705215] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mdadm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1705215

Title:
  invalid udev rules shipped in mdadm-udeb

Status in mdadm package in Ubuntu:
  Fix Released
Status in mdadm source package in Bionic:
  Fix Released
Status in mdadm source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Upon installation, RAID devices are not automatically assembled by
  default as they used to be. Instead of being presented with an
  assembled RAID array for installation, one is presented with
  individual disks which probably is not desired by the user, as most of
  the time RAID arrays are intentional.

  [Test Case]

   * Create a VM with e.g. two disks assembled in a Linux RAID1 using
  mdadm and not otherwise partitioned / empty.

   * Start the d-i based installer

   * In the partitioning screen one should be presented with a raid
  device to partition, not individual disks.

  [Regression Potential]

   * This is a regression in the bionic release versus Xenial behaviour

   * The udev rules as installed into the udeb package were not
  processed to substitute template variables for BINDIR location of the
  mdadm tools. Now the packaging was corrected to install identical udev
  rules into the deb and udeb package types.

  [Other Info]
   
   * Original bug report:

  It is not possible to install Ubuntu on RAID device with IMSM/DDF
  metadata. The installer asks if such arrays should be activated but
  fails to do it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mdadm 4.0-1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 19 09:46:44 2017
  InstallationDate: Installed on 2017-07-06 (12 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170702)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied
  MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: cannot open /dev/sda1: Permission denied
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=/dev/mapper/hostname--vg-root ro
  ProcMDstat:
   Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
   unused devices: <none>
  SourcePackage: mdadm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1705215/+subscriptions