yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

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

Title:
  Instance nics are reorder after reboot

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  In Progress

Bug description:
  Suppose I have 3 networks: a_network, g_network and z_network. When
  booting a new instance, through Horizon, I assign the networks are
  such: nic1=g_network, nic2=a_network and nic3=z_network. After the
  instance has been booted, I login and verify that all of the nics are
  assigned accordingly.

  Now I reboot the instance from Horizon. After the instance reboots I
  login and notice that nic1 is on the a_network, nic2 is on z_network
  and nic3 is on the g_network.

  I would have suspected that after rebooting the instance its nic to
  network mapping would have remained the same.

  Environment:
    * Nova version: Grizzly
    * Quantum for networking

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