Nodes fail deploying with 17.10 due to hang on "waiting for network" at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
maas (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Critical
|
Unassigned |
Bug Description
When I try to deploy an Artful image to nodes that previously deployed properly with 16.04, deployment fails due to timeout. It seems that the curtin install finishes successfully but the nodes are hanging at 'Waiting for network' on boot.
After looking into the image it seems as though MaaS/Curtin are setting the node up with '/etc/network/
Output of 'dpkg -l '*maas*'|cat':
||/ Name Version Architecture Description
+++-===
un maas <none> <none> (no description available)
ii maas-cli 2.2.2-6099-
ii maas-common 2.2.2-6099-
ii maas-dns 2.2.2-6099-
ii maas-proxy 2.2.2-6099-
ii maas-region-api 2.2.2-6099-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
ii python3-django-maas 2.2.2-6099-
ii python3-maas-client 2.2.2-6099-
ii python3-
Hi David,
The reason of the failure is because you need a newer curtin version. Artful has changed the way it does network (no longer e/n/i, but netplan) and as such, a newer curtin is needed to work alongside cloud-init to write the networking moving forward.