yahoo-eng-team team mailing list archive

[Dane LeBlanc <leblancd@xxxxxxxxx>]

Public bug reported:

Perform the following:
- Create a network
- Create a subnet (subnet 1) on the network
- Create a port on the network. (A fixed IP is allocated from subnet 1)
- Create a second subnet (subnet 2) on the same network
- Update port with fixed IP from subnet 2 (port has 2 fixed IPs)
- Update port to remove fixed IP from subnet 2 (port has 1 fixed IP)
- Delete subnet 2
= = = > 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'])

** Affects: neutron
     Importance: Undecided
     Assignee: Dane LeBlanc (leblancd)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Dane LeBlanc (leblancd)

-- 
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):
  New

Bug description:
  Perform the following:
  - Create a network
  - Create a subnet (subnet 1) on the network
  - Create a port on the network. (A fixed IP is allocated from subnet 1)
  - Create a second subnet (subnet 2) on the same network
  - Update port with fixed IP from subnet 2 (port has 2 fixed IPs)
  - Update port to remove fixed IP from subnet 2 (port has 1 fixed IP)
  - Delete subnet 2
  = = = > 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