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.
** Changed in: maas
Status: New => Incomplete
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
** Changed in: curtin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791006
Title:
deploying Ubuntu 18.04 with MAAS 1.9.5 fails during the final boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1791006/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
