This bug was fixed in the package livecd-rootfs - 2.395
---
livecd-rootfs (2.395) xenial; urgency=medium
* create /etc/cloud/cloud.cfg.d/99-snappy-disable-network-config.cfg on
snappy so we do not end up with broken network config after cloud-init
ran (LP: #1563296).
--
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => High
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) =>
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563296
The short term fix is to disable cloud-init's networking code by
writing a file /etc/cloud/cloud.cfg.d/99-snappy-disable-network-config.cfg
with:
| network:
|config: "disabled"
The file is yaml text.
This unfortunately, will
Hmm.
You can disable cloud-init writing network config by putting config in
/etc/cloud/cloud.cfg.d/ that says
network:
config: disabled
However, that will entirely disable cloud init writing networking
information that the data source provided it with.
Currently that is openstack config
