There is an option to update subnet of the external network that will be exclude IPs that are currently in use
Bug #1410171 reported by
Toni Freger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Opinion
|
Undecided
|
Unassigned |
Bug Description
During the verification of this RFE [1] I've encountered improper behavior.
When the subnet update is decreasing the number of IP's in the range, and FloatingIp is already in use, the update succeeds and the
excluded FloatingIp continue to function.
From the customer point of view I am also thinking that in the current situation the update should have failed.
To post a comment you must log in.
I think this behavior is probably preferred. There should be a away for the admin to update the allocation pool to affect future allocations. We don't want it to break existing floating IPs.
If the admin wants to get ride of allocations outside of the pool, he/she can then go delete them manually.