So I tihnk that the real solution for this bug is to somehow stop network devices from coming up until after cloud-init has searched for local datasources. There is still a case that would be odd if: - instance has /etc/network/interfaces configured for 'auto eth0' - instance has no local datasource - network datasource (openstack) had a network interfaces config for eth0.
at that point, the network would have already been up, and I'm really just not keen on bouncing networking. Perhaps in that case, write the network config and then reboot, to come back up configured correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
