NSX plugin can't reassociate floating ip to different IP on same port
Bug #1278581 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VMwareAPI-Team |
New
|
Medium
|
Unassigned | ||
neutron |
Fix Released
|
Medium
|
Salvatore Orlando |
Bug Description
the NSX plugin is unable to associate a floating IP to a different internal address on the same port where it's currently associated.
How to reproduce:
- create a port with two IPs on the same subnet (just because the fip needs to go through the same router)
- associate a floating IP with IP #1
- associate the same floating IP with IP#2
- FAIL!
This happens with this new test being introduced in tempest: https:/
summary: |
- NSX plugin can't reassociate floating ip to different IP on some port + NSX plugin can't reassociate floating ip to different IP on same port |
Changed in openstack-vmwareapi-team: | |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/72485
Review: https:/