Instance nics are reorder after reboot

Bug #1187092 reported by David Scannell on 2013-06-03
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
High
Aaron Rosen
Grizzly
High
Aaron Rosen

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

tags: added: network
Aaron Rosen (arosen) on 2013-06-28
Changed in nova:
assignee: nobody → Aaron Rosen (arosen)
importance: Undecided → High
Aaron Rosen (arosen) on 2013-06-28
Changed in nova:
status: New → Confirmed
Aaron Rosen (arosen) on 2013-06-28
tags: added: folsom-backport-potential grizzly-backport-potential

Fix proposed to branch: master
Review: https://review.openstack.org/35561

Changed in nova:
status: Confirmed → In Progress
tags: removed: grizzly-backport-potential

Reviewed: https://review.openstack.org/35561
Committed: http://github.com/openstack/nova/commit/bcd12a776e8cde8c4b64e7c1a21a7387ece55b31
Submitter: Jenkins
Branch: master

commit bcd12a776e8cde8c4b64e7c1a21a7387ece55b31
Author: Aaron Rosen <email address hidden>
Date: Tue Jul 9 14:35:17 2013 -0700

    Fix nic order not correct after reboot

    Previously if an instance was rebooted or migrated the original nic order
    would not be maintained. This patch retrieves the correct nic order from
    info_cache so that the order is mantained.

    Fixes bug 1187092

    Change-Id: I3f5488cc14c692fde7d5bd3376389e2f2f5550ff

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in nova:
milestone: none → havana-2
status: Fix Committed → Fix Released

Reviewed: https://review.openstack.org/37150
Committed: http://github.com/openstack/nova/commit/45fd6be08a04bc49dbc5c7fd67cdc7defb889284
Submitter: Jenkins
Branch: stable/grizzly

commit 45fd6be08a04bc49dbc5c7fd67cdc7defb889284
Author: Aaron Rosen <email address hidden>
Date: Mon Jul 15 17:32:43 2013 -0700

    Fix nic order not correct after reboot

    Previously if an instance was rebooted or migrated the original nic order
    would not be maintained. This patch retrieves the correct nic order from
    info_cache so that the order is mantained.

    Fixes bug 1187092

    Change-Id: I3f5488cc14c692fde7d5bd3376389e2f2f5550ff
    (cherry picked from commit bcd12a776e8cde8c4b64e7c1a21a7387ece55b31)

Thierry Carrez (ttx) on 2013-10-17
Changed in nova:
milestone: havana-2 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers