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

Bug #1319117 reported by David Moreau Simard
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

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 ?

Tags: network
Tracy Jones (tjones-i)
tags: added: network
Revision history for this message
Sean Dague (sdague) wrote :

What version of OpenStack? What's your nova.conf look like? Any setup configuration would be appreciated.

Changed in nova:
status: New → Incomplete
Revision history for this message
Diego Carrera Gallego (diegocarrera2000) wrote :

i got this bug on Openstack juno version.
nova version 2.19.0
Ubuntu 14.04

Changed in nova:
status: Incomplete → Confirmed
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.