Can't create floatingip with specified uuid

Bug #1640221 reported by Stefan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Undecided
sudhakar kumar srivastava

Bug Description

There are some cases in which we need to a rollback a delete floatingip action (e.g. some error in a specific L3 service implementation) and for that we basically require creating the old floatingip, including the uuid. The current L3_NAT_dbonly_mixin implementation generates the uuid every time create_floatingip is called so there's no way of re-creating a floatingip.

Tags: l3-ipam-dhcp
Revision history for this message
Andreas Scheuring (andreas-scheuring) wrote :

Hi Stefan, I would rather tackle the root causes that you described with "some error in a specific L3 service implementation". Can you elaborate more on that? Ideally you would directly open a bug for those issues providing the relevant information!

I'll set this to invalid. I'm not aware of any Neutron resource that allows specifying a UUID. And I don't see the use case. If you have a use case that is not related to buggy code, please elaborate here.

Thanks!

Changed in neutron:
status: New → Invalid
Revision history for this message
Stefan (stefan-apostoaie) wrote :

Our case is the following:
- we use a different component (controller) that handles the L3 requests and configures the compute nodes and routers and other components in the cloud
- our implementation for the L3 router plugin forwards the calls to our controller
- treating error cases for delete router, floatingip, etc calls in our L3 router plugin (e.g. the controller is unavailable for the moment, or some other error) involves doing a rollback (basically re-creating the exact same resource) to allow a retry in the future.
- the rollback works for router resource (it allows specifying a uuid on create router, see the l3_db.py in _create_router_db)
- the rollback for floatingips creates a different floatingip (different uuid) even if we specify the uuid.

I looked at other Neutron resources and creating network, port, router, and subnet with specified uuid is allowed. For floatingip this isn't allowed.

Changed in neutron:
status: Invalid → New
Revision history for this message
Andreas Scheuring (andreas-scheuring) wrote :

I'm sorry, I was just looking at the port object in the API doc - but there UUID is not listed. But it is listed in Networks. Seems like one can pass in a UUID for those resources, cool!

Changed in neutron:
status: New → Confirmed
tags: added: l3-ipam-dhcp
Changed in neutron:
assignee: nobody → sudhakar kumar srivastava (sudhakar.srivastava)
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.