I still have a similar issue on Newton release using Designate. When adding an instance with a floating ip i can get both records set. When i de-associate the floating ip designate correctly removes it. when i destroy the instance (nova destroy) without explicit floating ip deassociation it doesn't get removed from designate record list.
Any idea/workaround? ** Also affects: designate 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/997763 Title: floating ips are not disassociated from instances on deletion Status in Designate: New Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) essex series: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Precise: Fix Released Bug description: The following scenario does not work: nova add-floating-ip <instance> <floating_ip> nova delete <instance> nova "floating-ip-list" renders error like this: "The server has either erred or is incapable of performing the requested operation" This is because there's still mapping between the fixed ip of the deleted instance and floating ip left. Right now one must explicitly type: nova remove-floating-ip <instance> <floating_ip> nova delete <instance> To manage notifications about this bug go to: https://bugs.launchpad.net/designate/+bug/997763/+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