Public bug reported:
1.problem
Now there are no verifications about narrowing allocation pool of subnet.
so there are some vm which has the ips in a subnet, and the ips of vm belong to
the allocation pool of the subnet.
when we narrowed the range of allocation pool to ignore the ips of vm, Now the
operation can succeed,but there is no logic in this
2.solution
The ipaddress of vm in ipallocation must belong to a ipallocationpools when
narrowing the range of allocation pool.
we get the ipallocation from db
verify the allocation poll with the vm ips
if not ,raise IPAllocationNotInAllocationPools
** Affects: neutron
Importance: Undecided
Assignee: zhichao zhu (rtmdk)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhichao zhu (rtmdk)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1634330
Title:
add verification when narrowing allocation pool
Status in neutron:
New
Bug description:
1.problem
Now there are no verifications about narrowing allocation pool of subnet.
so there are some vm which has the ips in a subnet, and the ips of vm belong
to the allocation pool of the subnet.
when we narrowed the range of allocation pool to ignore the ips of vm, Now
the operation can succeed,but there is no logic in this
2.solution
The ipaddress of vm in ipallocation must belong to a ipallocationpools when
narrowing the range of allocation pool.
we get the ipallocation from db
verify the allocation poll with the vm ips
if not ,raise IPAllocationNotInAllocationPools
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1634330/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
