yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

*** This bug is a duplicate of bug 1064524 ***
    https://bugs.launchpad.net/bugs/1064524

** This bug has been marked a duplicate of bug 1064524
   Nic Ordering not guaranteed with Quantum API

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

Title:
  Creating multiple nics with --nic (and quantum) orders NICs randomly

Status in OpenStack Compute (Nova):
  New

Bug description:
  Description:

  When creating a machine on multiple networks with the nova command
  line, one does

  nova boot --image ed8b2a37-5535-4a5f-a615-443513036d71 --flavor 1
  --nic net-id= <id of first network>  --nic net-id= <id of first
  network>  test-vm1

  (http://docs.openstack.org/trunk/openstack-compute/admin/content
  /using-multi-nics.html)

  You expect to get the NICs attached to the VM in the same order
  (device 0 = first net listed, and so on, which - since they are
  usually all the one device type - corresponds with eth0, eth1, ... in
  Linux).  (Apparently this promise is not in that documentation, but I
  had it previously confirmed verbally from a core dev.)

  However, the guarantee is not always kept.  In a two nic machine, NICs
  sometimes get attached in reverse order.  Specifically seen with
  libvirt.

  Analysis:

  This is probably not an issue for many users.  If you're using DHCP on
  both interfaces, you'll get appropriate address and route setups and
  may not care which interface is on which network.   If, however, DHCP
  is turned off, or you're attached to two provider networks, it's not
  possible to distinguish which network is which, so the ordering is
  required.

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