| 2016-03-01 20:12:19 |
Scott Moser |
bug |
|
|
added bug |
| 2016-03-01 20:12:19 |
Scott Moser |
attachment added |
|
boot serial log https://bugs.launchpad.net/bugs/1551937/+attachment/4585887/+files/boot.log |
|
| 2016-03-01 20:13:48 |
Scott Moser |
attachment added |
|
curtin storage config https://bugs.launchpad.net/curtin/+bug/1551937/+attachment/4585888/+files/curtin-config.yaml |
|
| 2016-03-02 00:45:10 |
Scott Moser |
curtin: status |
New |
Confirmed |
|
| 2016-03-02 00:45:12 |
Scott Moser |
curtin: importance |
Undecided |
High |
|
| 2016-03-02 14:25:57 |
Scott Moser |
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!
$ 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 |
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
$ 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 |
|
| 2016-03-02 15:08:26 |
Scott Moser |
attachment added |
|
attaching a patch that i'm testing right now. hacky. https://bugs.launchpad.net/curtin/+bug/1551937/+attachment/4586613/+files/out.diff |
|
| 2016-03-02 16:57:50 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/curtin/trunk.lp1551937 |
|
| 2016-03-02 17:53:35 |
Scott Moser |
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
$ 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 |
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 |
|
| 2016-06-22 14:41:34 |
Ryan Harper |
branch linked |
|
lp:~raharper/curtin/trunk.vmtest-multipath |
|
| 2016-06-22 14:41:48 |
Ryan Harper |
tags |
|
curtin-sru |
|
| 2016-06-22 14:42:22 |
Ryan Harper |
curtin: status |
Confirmed |
In Progress |
|
| 2016-06-24 19:47:13 |
Launchpad Janitor |
branch linked |
|
lp:curtin |
|
| 2016-07-06 14:41:31 |
Ryan Harper |
curtin: status |
In Progress |
Fix Committed |
|
| 2016-07-12 16:14:48 |
Launchpad Janitor |
branch linked |
|
lp:~raharper/ubuntu/xenial/curtin/pkg-sru-revno399 |
|
| 2016-07-12 16:33:34 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/yakkety/curtin/pkg |
|
| 2016-07-12 16:33:46 |
Launchpad Janitor |
branch linked |
|
lp:~raharper/ubuntu/xenial/curtin/pkg-sru-revno399 |
|
| 2016-07-12 22:12:57 |
Ryan Harper |
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 |
[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 |
|
| 2016-07-13 13:57:33 |
Martin Pitt |
bug task added |
|
curtin (Ubuntu) |
|
| 2016-07-13 13:57:50 |
Martin Pitt |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-07-13 13:57:50 |
Martin Pitt |
bug task added |
|
curtin (Ubuntu Xenial) |
|
| 2016-07-13 13:58:01 |
Martin Pitt |
curtin (Ubuntu): status |
New |
Fix Released |
|
| 2016-07-13 13:58:13 |
Martin Pitt |
curtin (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-07-13 13:58:15 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-07-13 13:58:16 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-07-13 13:58:19 |
Martin Pitt |
tags |
curtin-sru |
curtin-sru verification-needed |
|
| 2016-07-19 19:06:54 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/trusty/curtin/trusty-proposed |
|
| 2016-07-21 19:15:11 |
Brian Murray |
curtin (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2016-07-30 04:26:11 |
Mathew Hodson |
curtin (Ubuntu): importance |
Undecided |
High |
|
| 2016-07-30 04:26:13 |
Mathew Hodson |
curtin (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2016-07-30 04:26:15 |
Mathew Hodson |
curtin (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-08-16 21:58:28 |
Brian Murray |
tags |
curtin-sru verification-needed |
curtin-sru verification-done |
|
| 2016-08-17 13:01:18 |
Launchpad Janitor |
curtin (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-08-17 13:01:29 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-08-17 13:01:50 |
Launchpad Janitor |
curtin (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-12-15 22:10:13 |
Scott Moser |
curtin: status |
Fix Committed |
Fix Released |
|
