Public bug reported:
When the user provisions a bionic VM the first time, cloudinit picks
netplan as the renderer since other renderers are not available (e.g.,
eni). Cloudinit then wrote a netplan file (50-cloud-init.yaml). If the
user installs ifupdown and fail to manually remove netplan, the vm will
fail to boot if there are conflicting changes happened to the NIC, such
as a MAC address change. The reason is that when ifupdown is installed
cloudinit will prefer eni at boot time and the previously written
netplan configuration file now contains bad network configuration.
This was discussed in cloud-init IRC channel and the general consensus
is that while the user should be removing netplan when installing
ifupdown, it is not a hard requirement as netplan and ifupdown can
actually coexist. Cloudinit should consider removing conflicting netplan
file that it wrote when it chooses eni.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832381
Title:
vm fails to boot due to conflicting network configuration when user
switches from netplan to eni
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
