yahoo-eng-team team mailing list archive

[Miguel Lavalle <2040457@xxxxxxxxxxxxxxxxxx>]

As you can see in the unit test failures of your proposed patch
(https://739b5b5aed9a6d447975-907323b417218f46df6192f35c6995f8.ssl.cf2.rackcdn.com/899373/1/check/openstack-
tox-py39/5433f4e/testr_results.html), the possibility of having subnet
empty allocation pools has long been assumed as valid behavior in the
Neutron API. That expected behavior should not be changed just because
in "your opinion", as indicated in your comment above, another behavior
is desirable.

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

** Changed in: neutron
       Status: Won't Fix => 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/2040457

Title:
  [allocation_pools] Need re-generation  new pools from cidr and
  gateway-ip after update one subnet with empty 'allocation_pools'

Status in neutron:
  Invalid

Bug description:
  We found that allocation_pools is empty list after update subnet with empty 'allocation_pools':
   neutron subnet-show f84d8c24-251c-4a28-83a0-6c7f147c3da1
  +-------------------+--------------------------------------+
  | Field             | Value                                |
  +-------------------+--------------------------------------+
  | allocation_pools  |                                      |
  | cidr              | 192.168.123.0/24                     |

  In my opinion, if we clear the allocation_pools of one subnet, it
  should re-generation new allocation_pools by the cidr and gateway-ip
  of the subnet.

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