I discussed this with cgregan on IRC and I think we came to the
conclusion that the MAAS/curtin bug is simply that the two kernels
(commissioning vs. ephemeral deployment) gather different (or missing)
unique identifiers for each drive.
To validate that, I would run the following on each kernel on the
problematic systems:
find /dev/disk -type l | xargs ls -1l | awk '{ print $9, $10, $11 }' |
sort -k2
This will tell us which unique identifiers each kernel found to identify
each disk, and sort by the endpoint block device, to make it easier to
identify what might be missing for each drive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651602
Title:
[2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Status in MAAS:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1)
Deploying Xenial Nodes
1) Deploy MAAS 2.1.1 on Yakkety
2) Associate Juju 2.1 beta3
3) Juju deploy Kubernetes Core
Nodes begin to deploy but fail
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n"
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
