I'm going to mark this fix-released.
The general bug as described in the description is that cloud-init can't
correctly apply networking for all interfaces.
cloud-init local applies networking configuration to the system, and
should apply before the system brings networking up. Thus appearing to
the system as if the networkign config was already there, and should be
brought up properly as it would be on reboot.
If you think this bug is not fixed, its probably best to file a new bug,
describe the problem, and attach output of 'cloud-init collect-logs'.
** Changed in: ubuntu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1225922
Title:
Support static network configuration even on already configured
devices
Status in Ubuntu:
Fix Released
Status in linux-gcp package in Ubuntu:
Confirmed
Bug description:
Some datasources (e.g. OpenNebula) support full static network
configuration. It's done in local execution phase by pushing new
interfaces configuration to *distro.apply_network*. This new
configuration is written on disk and activated by calling ifup on
particular devices. Unfortunatelly it can't be guaranteed that full
local phase is executed before any network configuration is done by
system. Mentioned steps are OK only for devices not present in former
network configuration or not configurated to start on boot (e.g. eth0
configured on boot to take address from DHCP, the new static
configuration is not applied on this device, it's already up and ifup
just passes).
It would be good to first put interfaces down before writing new
configuration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1225922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
