Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1640221
Title:
Can't create floatingip with specified uuid
Status in neutron:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640221/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
