yahoo-eng-team team mailing list archive

[Paul Ward <wpward@xxxxxxxxxx>]

It's been decided to abandon this fix because it's preventing something
that, while not useful, is technically "ok".  The better place for this
fix would be in the UI as a hint to the user.

For more info: http://lists.openstack.org/pipermail/openstack-
dev/2014-January/025385.html

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  Neutron should disallow a CIDR of /32

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  NeutronDbPluginV2._validate_allocation_pools() currently does basic
  checks to be sure you don't have an invalid subnet specified.
  However, one thing missing is checking for a CIDR of /32.  Such a
  subnet would only have one valid IP in it, which would be consumed by
  the gateway, thus making this network a dead network since no IPs are
  left over to be allocated to VMs.

  I propose a change to disallow start_ip == end_ip in
  NeutronDbPluginV2._validate_allocation_pools() to cover the CIDR of
  /32 case.

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