nova list show incorrect when neutron re-assign floatingip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
ZongKai LI | ||
Icehouse |
New
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
boot more several instances, create a floatingip, when re-assign the floatingip to multi instances, nova list will show incorrect result.
>>>neutron floatingip-
>>>neutron floatingip-
>>>neutron floatingip-
>>>nova list
(nova list result will be like:)
-------
instance0 fixedip0, floatingip
instance1 fixedip1, floatingip
instance2 fixedip2, floatingip
instance0,1,2, they all have floatingip, but run "neutron floatingip-list", we can see it only bind to instance2.
another situation is that after a few time(half a min, or longer), "nova list" can show correct result.
-------
instance0 fixedip0
instance1 fixedip1
instance2 fixedip2, floatingip
description: | updated |
Changed in neutron: | |
status: | Fix Committed → In Progress |
Changed in neutron: | |
importance: | Undecided → Low |
Changed in neutron: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-1 → 2015.1.0 |
it's neutron's problem.
the operation in bug description is floating ip re-assignment, this can depart into two steps, disassociate from origin port, associate to new port; when re-assign floating ip, network changes happened on two(origin, new) instance's port, but neutron only send event for new instance port;
add code ensure neutron will first send event for origin/disassociate one, then send event for new/associate one, will fix this.