yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

marking fix-commited in cloud-init as revno 1225.
fix released in yakkety images and will make it back to xenial via sru.

** Changed in: cloud-init
       Status: Confirmed => Fix Committed

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1315501

Title:
  cloud-init does not use interfaces.d in trusty

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Reference/context: https://ask.openstack.org/en/question/28297/cloud-
  init-nonet-waiting-and-fails/

  The trusty image provided by http://cloud-images.ubuntu.com/trusty/ contains an eth0 interface configured as dhcp in /etc/network/interfaces.d/eth0.cfg.
  When I boot this image in an Openstack non-dhcp networking environment, cloud-init configures the static IP provided by Neutron directly in /etc/network/interfaces (not interfaces.d).

  This means I now have two eth0 devices configured, in two different files.
  Booting 20 VMs with the same image yields around 50-60% of VMs that are not reachable by network.

  Soft rebooting a VM in this state or doing and "ifdown eth0 && ifup
  eth0" will make it ping.

  I removed the the eth0 interface file in
  /etc/network/interfaces.d/eth0.cfg from the image, booted another
  round of VMs and all of them worked fine.

  Now, I see three possible outcomes:
  - If eth0 is present in /etc/network/interfaces.d, cloud-init configures/re-configures that interface
  - If eth0 is present in /etc/network/interfaces.d, cloud-init deletes it and configures /etc/network/interfaces
  - Ubuntu cloud images ships without eth0 being configured by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1315501/+subscriptions