yahoo-eng-team team mailing list archive

[David Moreau Simard <dmsimard@xxxxxxxx>]

Public bug reported:

I filed a bug in cloud-init that describes the issue here:
https://bugs.launchpad.net/cloud-init/+bug/1315501

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 (using config drive), cloud-init configures the static IP provided by Neutron directly in /etc/network/interfaces (not interfaces.d) with the nova interface template.

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.

Perhaps nova could realize that eth0 is already configured and do
something according to that ?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1319117

Title:
  Ubuntu trusty: Interface template is injected even if the interface
  exists elsewhere

Status in OpenStack Compute (Nova):
  New

Bug description:
  I filed a bug in cloud-init that describes the issue here:
  https://bugs.launchpad.net/cloud-init/+bug/1315501

  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 (using config drive), cloud-init configures the static IP provided by Neutron directly in /etc/network/interfaces (not interfaces.d) with the nova interface template.

  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.

  Perhaps nova could realize that eth0 is already configured and do
  something according to that ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1319117/+subscriptions