yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

This is by-design behavior: deletion includes disassociation. 
I think you could ask a question in openstack-dev mailing list or ask.openstack.org about the reasoning behind this.


** Tags added: l3-ipam-dhcp

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1394456

Title:
  Deleting floating ip also disassociates the floating ip on active
  instances without a warning

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  I had associated a floating IP to an instance and then I deleted the
  floating ips under the access & security panel from the dashboard.

  I don't know if it is by design but I was expecting some sort of a
  warning saying that the "floating IP is in use" and not allow the
  deletion. Similar to how subnet cannot be deleted if there are active
  instances.

  If this is not a valid bug, I would like to know why it isn't.

  - Prasoon

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1394456/+subscriptions