yahoo-eng-team team mailing list archive

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

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

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

Title:
  subnet-delete should fail if the subnet is attached to a router

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

Bug description:
  This is related to bug 1152050.

  Deleting a subnet attached to a router interface could cause some issues.
  From a quantum perspective this will detach the subnet from the router, as in router-remove-interface, but it will also leave configuration related to that subnet on the router.

  For instance the L3 agent will still have the IP address.

  A quick fix would be to remove network:router_interface from
  AUTO_DELETE_PORT_OWNERS.

  However, I recall that it was explicitly added there for a reason.
  Also, this will cause a change in the API behaviour which might break
  clients (it is likely people have developed application leveraging the
  fact you can delete a subnet without having to remove the gateway port
  first).

  A more convoluted fix would consist in triggering the remove interface
  action when a subnet is deleted. The problem with this approach is
  that this will violate the principle of 'atomicity' of Quantum
  operations: If I ask for deleting a subnet, I should only delete the
  subnet or get an error.

  I would vote for preventing deletion, but I'm a bit nervous about
  doing this change so close to the release.

  I am keeping this targeted to grizzly-rc1 for discussion. If no consensus is achieve we can move to havana.
  The fix for bug 1152050 mitigates the impact of this issue.

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