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 drive or NoCloud.
But in the future it will be other sources. Basically, the cloud can provide
the intended networking to the instance, and the instance should apply it.
2 options I can think of are
1 adding function for cloud-init to not write 'fallback' networking config but
still write carapace provided config
2 having cloud init read and render the snappy provided config
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563296
Title:
cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in
/etc/network/interfaces.d/ in snappy leaving the boot completely
network-less
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1563296/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
