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
** Changed in: maas
Status: Incomplete => Expired
--
You received this bug notification because you are a
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
Can we confirm which version of curtin you have installed?
** Changed in: curtin (Ubuntu Trusty)
Status: New => Incomplete
--
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:
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
