multipath-install: Installing with multipath enabled does not install multipath-tools

[Stefan Bader]

Vivid serve iso 2015-04-17

When installing with disk-detect/multipath/enable=true it would be sensible to automatically install multipath-tools(-boot?) along with a /etc/multipath.conf that was used by the installer. There also seems to be a delta between the kpartx command used and the one used by default. The installer creates and uses /dev/mapper/<mpath>p<num> while multipath-tools create /dev/mapper/<mpath>-part<num>. This causes problems on boot as /boot is always directly mounted (assuming the default LVM install).

Related bugs:
 * bug 1371634: curtin block devices appear twice [install does not use multipath]

[Scott Moser (smoser)]

Related/possibly duplicate bug is bug 1371634.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mike Rushton (leftyfb)]

I have tried the latest curtin-common and python-curtin from the wily repositories running on 14.04.2:

#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1.0~bzr201-0ubuntu1~14.04.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
     0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
        500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
     0.1.0~bzr126-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy python-curtin
python-curtin:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1.0~bzr201-0ubuntu1~14.04.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
     0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
        500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
     0.1.0~bzr126-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy maas
maas:
  Installed: 1.7.5+bzr3369-0ubuntu1~trusty1
  Candidate: 1.7.5+bzr3369-0ubuntu1
  Version table:
     1.7.5+bzr3369-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
 *** 1.7.5+bzr3369-0ubuntu1~trusty1 0
        500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status
     1.5.4+bzr2294-0ubuntu1.3 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
     1.5.4+bzr2294-0ubuntu1.2 0
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
     1.5+bzr2252-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The deployment never fully boots up. It never gets to a console or allows an ssh connection. Attached is a log of the deployment and first boot process to debug.

[Scott Moser (smoser)]

I dropped the curtin task from this bug as bug 1371634 has more info on it. I'll leave this for d-i.