← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1271311] [NEW] Neutron should disallow a CIDR of /32

 

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Paul Ward (wpward)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Paul Ward (wpward)

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

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


Follow ups

References