Comment 0 for bug 1551937

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!

$ 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