Can't create floatingip with specified uuid
Bug #1640221 reported by
Stefan
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.
Changed in neutron: | |
status: | Invalid → New |
Changed in neutron: | |
assignee: | nobody → sudhakar kumar srivastava (sudhakar.srivastava) |
To post a comment you must log in.
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!