yahoo-eng-team team mailing list archive

[Carl Baldwin <carl@xxxxxxxxxxxxx>]

This is by design.  John Kasperski's assessment is correct.  The
allocation pool is not meant to prevent ports from being created outside
of it.  It only exists to restrict automatic allocation of IP addresses
by Neutron.

I don't think the situation warrants a warning.  If anything, better
documentation.

** Changed in: neutron
       Status: In Progress => Won't Fix

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

Title:
  subnet-update of allocation_pool does not prevent orphaning existing
  ports

Status in neutron:
  Won't Fix

Bug description:
  An error should be returned when subnet-update is used to modify the
  allocation_pool such that existing neutron ports are no longer
  included.   This operation should not be permitted.

  Currently the existing allocated neutron ports are not verified when a
  subnet allocation pool is changed.  This can lead to unusual
  statistics such as:   there could be 50 allocated neutron objects
  associated with a subnet, however the allocation pool range only
  includes 10 IP addresses and all 10 of those are not allocated.

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