Disassociate Floating IP from an instance with 2 NICs doesn't work
Bug #1265872 reported by
marcos.gm
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
George Peristerakis | ||
Havana |
Fix Released
|
Medium
|
Julie Pichon |
Bug Description
An instance with two internal networks configured, and a floating IP associated, cannot release the Floating IP because a message 'No floating IP's to disassociate' pops-up
As a result, the instance keeps its floating IP
Openstack version: Havana installed via Packstack (on Centos6)
[root@compute2 ~]# nova --version
2.15.0
[root@compute2 ~]# neutron --version
2.3.1
Screenshots attached (in them, the floating IP is 192.168.1.59)
Changed in horizon: | |
assignee: | nobody → George Peristerakis (george-peristerakis) |
Changed in horizon: | |
importance: | Undecided → Medium |
Changed in horizon: | |
milestone: | none → icehouse-3 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
tags: | added: havana-backport-potential |
Changed in horizon: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
I traced the problem down to the function api.neutron. FloatingIpManag er.get_ target_ id_by_instance. The function returns the first ip in the list. This function should be returning a list of ips associated to the instance.