deploying Ubuntu 18.04 with MAAS 1.9.5 fails during the final boot

[Paul Collins]

I have a bunch of machines here enlisted in a MAAS 1.9.5 that commissioned happily. Deploying Ubuntu 16.04 to them works fine too, and they continue working when d-r-u'd to 18.04.

However, deploying 18.04 directly fails -- the nodes boot into the installer successfully and reboot at the end, but then when they boot into the final installation they fail to get network and MAAS eventually transitions the node to "Failed deployment". Here's the console log from such a final boot (Canonical-only link): https://pastebin.canonical.com/p/R8Fykv6nph/

I talked with mpontillo about this on IRC, and we tried a few things with no success. I booted a failed node with init=/bin/bash and discovered that /etc/netplan was empty rather than containing 50-cloud-init.yaml as expected.

I've run cloud-init collect-logs and updated the result (Canonical-only link): https://private-fileshare.canonical.com/~pjdc/alnilam.cloud-init-logs.tar.gz

[Andres Rodriguez (andreserl)]

I think the issue is quite simple actually.

Bionic uses net plan, everything before that uses e/n/i. In trusty, curtin wrote the network configuration. In latest versions, Curtin now doesn’t do the network configuration, and actually tells cloud-unit to do it by passing the configuration.

So what I think is happening is that curtin writes e/n/i and cloud-unit actually never writes net plan.

So I would say that bionic deployment is not supported on 1.9 due to curtin.

[Ryan Harper (raharper)]

Can we confirm which version of curtin you have installed?

[Paul Collins (pjdc)]

Assuming you mean on the MAAS machines, here's the cluster controller (same on the region controller):

pjdc@barberry:~$ dpkg-query -W curtin curtin-common python-curtin
curtin
curtin-common 0.1.0~bzr399-0ubuntu1~14.04.1
python-curtin 0.1.0~bzr399-0ubuntu1~14.04.1
pjdc@barberry:~$ apt-cache policy curtin curtin-common python-curtin
curtin:
  Installed: (none)
  Candidate: 0.1.0~bzr399-0ubuntu1~14.04.1
  Version table:
     0.1.0~bzr399-0ubuntu1~14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
     0.1.0~bzr126-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
curtin-common:
  Installed: 0.1.0~bzr399-0ubuntu1~14.04.1
  Candidate: 0.1.0~bzr399-0ubuntu1~14.04.1
  Version table:
 *** 0.1.0~bzr399-0ubuntu1~14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1.0~bzr126-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
python-curtin:
  Installed: 0.1.0~bzr399-0ubuntu1~14.04.1
  Candidate: 0.1.0~bzr399-0ubuntu1~14.04.1
  Version table:
 *** 0.1.0~bzr399-0ubuntu1~14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1.0~bzr126-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
pjdc@barberry:~$

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team