[Bug 1316357] [NEW] Network interface IP address not set on first boot if config drive used

[Simeon Monov]

Public bug reported:

I'm trying to deploy an Ubuntu cloud image (I hit same issue on all
Ubuntu images available from http://cloud-images.ubuntu.com/) on a non
DHCP network in Open Stack environment using config drive.

Cloud init local successfully sets the /etc/network/interfaces file but
does not reloads the interface and the virtual machine never gets an IP.
If the VM is rebooted (or networking manually restarted from console)
then Ubuntu picks up the new interface configuration and everything is
working as excepted.

The image itself has a configured eth0 interface set for dhcp. If I
delete this configuration (from /etc/network/interfaces.d/eth0.cfg) from
the image then everything works as expected.

After multiple tests in different Open Stack deployments I can confirm
that this issue is intermittent. Sometimes the image would pickup the
new IP but most of the time it wont and needs VM reboot in order to get
the network configured.

After some more debugging I think that there is some timing issue in the
init scripts boot process on Ubuntu where the networking init scripts
will try to contact the dhcp to get an IP but in the same time the
cloud-init-local will setup the network and the networking scripts will
never find out that the interface was changed from DHCP to static.

The latest image I tested is:

Ubuntu Server 14.04 LTS cloud image from 5/5/2014 (the bug exists with
all the cloud images available)

and

cloud-init 0.7.5-0ubuntu1

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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