Public bug reported: 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. [1] https://bugs.launchpad.net/neutron/+bug/1111572 ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1410171 Title: There is an option to update subnet of the external network that will be exclude IPs that are currently in use Status in OpenStack Neutron (virtual network service): New 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. [1] https://bugs.launchpad.net/neutron/+bug/1111572 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1410171/+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
