yahoo-eng-team team mailing list archive

[Dane LeBlanc <leblancd@xxxxxxxxx>]

Public bug reported:

With the current Neutron implementation, a subnet cannot be deleted
until all associated IP addresses have been removed from ports (via
port update) or the associated ports/VMs have been deleted.	

In the case of SLAAC-enabled subnets, however, it's not feasible to
require removal of SLAAC-generated addresses individually from each
associated port before deleting a subnet because of the multicast
nature of RA messages. For SLAAC-enabled subnets, the processing of
subnet delete requests needs to be changed so that these subnets will
be allowed to be deleted, and all ports get disassociated from their
corresponding SLAAC IP address, when there are ports existing
on the SLAAC subnet.

** Affects: neutron
     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/1393435

Title:
  Subnet delete for IPv6 SLAAC should not require prior port disassoc

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  With the current Neutron implementation, a subnet cannot be deleted
  until all associated IP addresses have been removed from ports (via
  port update) or the associated ports/VMs have been deleted.	

  In the case of SLAAC-enabled subnets, however, it's not feasible to
  require removal of SLAAC-generated addresses individually from each
  associated port before deleting a subnet because of the multicast
  nature of RA messages. For SLAAC-enabled subnets, the processing of
  subnet delete requests needs to be changed so that these subnets will
  be allowed to be deleted, and all ports get disassociated from their
  corresponding SLAAC IP address, when there are ports existing
  on the SLAAC subnet.

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