Cannot Disassociated Autoallocated floating ip

Bug #1150772 reported by seth vidal on 2013-03-07
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
High
hzxiongwenwu

Bug Description

When you've allocated a floating ip to an instance you cannot disassociate the old ip from the instance.

Any attempt to do so ends in an error.

You should be able to disassociate the auto-allocated floating ip from an instance.

Russell Bryant (russellb) wrote :

Can you include the details of the error you get? Thanks

Changed in nova:
status: New → Incomplete
seth vidal (skvidal) wrote :

As admin:

nova remove-floating-ip dfc2c868-75eb-4c77-bb5c-6892240098ed 209.132.184.154

ERROR: Cannot disassociate auto assigned floating ip (HTTP 403) (Request-ID: req-cbafd77d-92e0-4ee4-b462-82dc4bf3fefe)

that instance has:

 vlannet_5=172.16.5.3, 209.132.184.143, 209.132.184.154 |

the first ip there is the one I associated with it from my set of floating ips I'd allocated before.

I need this instance to have a persistent ip across many instantiations and reboots.

I don't need 2 external ips allocated to it.

Changed in nova:
status: Incomplete → Confirmed
importance: Undecided → High
milestone: none → grizzly-rc1
Édouard Thuleau (ethuleau) wrote :

Nova doesn't authorize to delete an auto assigned floating IP. As was explained in this bug https://bugs.launchpad.net/nova/+bug/1061499
You got the same problem without attache a second floating IP to the VM interface.

But in bug https://bugs.launchpad.net/nova/+bug/1061499, Dan Prince (comment #1) asks to reconsider treating auto-assigned floating IPs just like we do normal floating IPs and allow them to be unassigned. So we can use this bug to discuss it and if we are OK, to implement it

Édouard Thuleau (ethuleau) wrote :

Another bug related to this topic https://bugs.launchpad.net/nova/+bug/1017379
Perhaps we can link these bugs ?

Changed in nova:
assignee: nobody → Édouard Thuleau (ethuleau)
Russell Bryant (russellb) wrote :

After looking at this and talking about it more, I don't think this is something we can rush in for grizzly. We need more time to look at all the ways that auto assigned floating IPs are special cased and make sure we're not breaking things if we change it.

Changed in nova:
milestone: grizzly-rc1 → none
no longer affects: nova/folsom

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

Changed in nova:
status: Confirmed → In Progress
Édouard Thuleau (ethuleau) wrote :

I made a fix which authorize to disassociate an auto-assigned floating IP on a server.
- the auto-assigned floating IP is listed in floating IP list
- when an auto-assigned floating IP is unassigned from a server, it is automatically deallocated from the project
- when a server with an auto-assigned floating IP is deleted, the auto-assigned floating IP is automatically deallocated from the project

Changed in nova:
status: In Progress → Confirmed
assignee: Édouard Thuleau (ethuleau) → nobody
hzxiongwenwu (xwwzzy) on 2014-06-18
Changed in nova:
assignee: nobody → hzxiongwenwu (xwwzzy)
hzxiongwenwu (xwwzzy) wrote :

I can not reproduce it

Joe Gordon (jogo) on 2014-06-19
Changed in nova:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers