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 -- 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: Invalid 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 : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp