Instance nics are reorder after reboot
Bug #1187092 reported by
David Scannell
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Aaron Rosen | ||
Grizzly |
Fix Released
|
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 |
Changed in nova: | |
assignee: | nobody → Aaron Rosen (arosen) |
importance: | Undecided → High |
Changed in nova: | |
status: | New → Confirmed |
tags: | added: folsom-backport-potential grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/35561
Review: https:/