Is there any progress on this bug ? The solution/workaround I am currently using for this issue is that it appears if any network interface is configured prior to cloud-init running, that interface has an ifup done before cloud-init ever starts. Cloud-init then replaces the information for the network interfaces with the information from the datasource. Cloud-init then calls an ifup. This ifup is a no-op if that interface was already up prior to cloud-init starting. If Cloud-init instead does an 'ifdown' then 'ifup' after writing the network interfaces, the interface will come up as expected, reading the new network interface information. BTW, this same scenario happens with RHEL and SLES so maybe the fix could be done at a baseclass level.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1316357 Title: Network interface IP address not set on first boot if config drive used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1316357/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
