Exact same bug as https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1315501
Workaround given by David Moreau Simard works:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1315501/comments/11
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
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/b
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 dat
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
