group.of.nepali.translators team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1551937

Title:
  lvm and multipath and xenial not happy together

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * MaaS deployments to systems with multipath configures cannot
     install Xenial releases due to a change in how multipath configures
     its friendly names.  On older releases (multipath-tools < 0.5.0)
     multipath-tools expects that the names of the devices will include
     names and parses the file with that expectation. However, on newer
     releases (multipath-tools >= 0.5.0) multipath-tools uses spaces to
     separate fields in the bindings file and fails if the device name
     includes spaces. 

     Curtin will detect the level of multipath-tools to be used in the
     target OS and adjusts how it generates device names for the binding
     file accordingly.
     
  [Test Case]

   * Install proposed curtin package and deploy custom storage
     configuration against a Power8 or similiar configured multipath
     system and select Xenial as the target OS.

    PASS: The multipath configured machine will successfully install
    both Xenial and Trusty.

    FAIL: The multipath configured machine will fail to install Xenial
    but will successfully install Trusty.

  [Regression Potential]

   * May impact users of systems with multipath storage configurations.

  
  [Original Description]

  tried deploy of xenial with curtin on a powerNV system.  the result was failure to mount the root, ending like this:
  Begin: Running /scripts/local-block ...   lvmetad is not active yet, using direc
  t activation during sysinit
    Volume group "mpath0" not found
    Cannot process volume group mpath0
  done.
  Begin: Running /scripts/local-block ...   lvmetad is not active yet, using direct activation during sysinit
    Volume group "mpath0" not found
    Cannot process volume group mpath0
  done.
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
     - Check rootdelay= (did the system wait long enough?)
     - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  /dev/mapper/mpath0-part2 does not exist.  Dropping to a shell!

  Related bugs:
   * bug 1429327: Boot from a unique, stable, multipath-dependent symlink
   * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers
   * bug 1552319: xenial kernel boot slow/timeout on power8 powerNV

  $ dpkg-query --show | egrep '(maas|curtin)'
  curtin-common   0.1.0~bzr359-0ubuntu1
  maas    1.9.1+bzr4541-0ubuntu1~trusty1
  maas-cli        1.9.1+bzr4541-0ubuntu1~trusty1
  maas-cluster-controller 1.9.1+bzr4541-0ubuntu1~trusty1
  maas-common     1.9.1+bzr4541-0ubuntu1~trusty1
  maas-dhcp       1.9.1+bzr4541-0ubuntu1~trusty1
  maas-dns        1.9.1+bzr4541-0ubuntu1~trusty1
  maas-provision  2.2.2-0ubuntu4
  maas-provision-common   2.2.2-0ubuntu4
  maas-proxy      1.9.1+bzr4541-0ubuntu1~trusty1
  maas-region-controller  1.9.1+bzr4541-0ubuntu1~trusty1
  maas-region-controller-min      1.9.1+bzr4541-0ubuntu1~trusty1
  python-curtin   0.1.0~bzr359-0ubuntu1
  python-django-maas      1.9.1+bzr4541-0ubuntu1~trusty1
  python-maas-client      1.9.1+bzr4541-0ubuntu1~trusty1
  python-maas-provision   2.2.2-0ubuntu4
  python-maas-provisioningserver  1.9.1+bzr4541-0ubuntu1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1551937/+subscriptions