← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1483103] Re: When subnetpool didn't follow the cidr's prefix which input at the subnetpool creation.

 

** Changed in: neutron
       Status: New => 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/1483103

Title:
  When subnetpool didn't follow the cidr's prefix which input at the
  subnetpool creation.

Status in neutron:
  Invalid

Bug description:
  I create subnetpool like:
  neutron subnetpool-create --pool-prefix 6.6.6.6/24 --pool-prefix 9.9.9.9/30 --pool-prefix 8.8.8.8/20 test2
  And then I create a subnet from this subnetpool.The returned message is like:
  neutron subnet-create test --subnetpool test2
  Failed to allocate subnet: Insufficient prefix space to allocate subnet size /8

  But when it contains *.*.*.*/8 which the prefixlen is 8 . Just like:
  neutron subnetpool-create --pool-prefix 6.6.6.6/8 --pool-prefix 9.9.9.9/30 --pool-prefix 8.8.8.8/20 test2
  And the subnet creation will be success.

  The subnetpool's default_prefixlen is always 8.And this may make user to input cidr which the prefixlen is 8.
  I think when use the subnetpool to create subnet, it should get one of pool and cannot limit according to the default prefixlen.

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


References