yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

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

Title:
  Delete subnet fails if assoc port has IPs from another subnet

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  Perform the following:
  - Create a network
  - Create two subnets on the network
  - Create a port on the network using a fixed IP from one of the subnets
  - Delete the other subnet
  = = = > FAILURE: Subnet delete fails because SUPPOSEDLY there
  are port(s) still associated with that subnet.

  Looking at delete_subnet() in neutron/db/db_base_plugin_v2.py,
  the check for port(s) still being associated with that _subnet_
  is actually checking for port(s) still being associated with
  the _network_ (not the subnet), i.e. it's doing a:
      filter_by(network_id=subnet.network_id)
  rather than a:
      filter_by(subnet_id=subnet['id'])

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