Public bug reported: Now floating IP can be disassociated via two different API data dict: {'port_id': null} or a dict without `port_id` key.
And, floating IP can not be updated with its original port_id, you may get some bad request exception. Which will cause some know issues: 1. Updating floating IP extra attributes, for instance description, will unexpectedly disassociate it. This behavior will interrupt the user's service traffic. And this is because that user can submit an empty request dict (without port_id parameter) for the floating IP updating API, and then it will be disassociated by default. 2. If user try to update floating IP extra attribute with port_id that it associated with, the neutron API will return a bad request exception. So there is no way to update the floating IP extra attributes without changing it's association. And there is already a bug for the updating floating IP extra attributes issue: https://bugs.launchpad.net/neutron/+bug/1578523 This bug will be used to handle the API behavior issues. ** Affects: neutron Importance: Undecided Status: New ** Description changed: Now floating IP can be disassociated via two different API data dict: {'port_id': null} or a dict without `port_id` key. And, floating IP can not be updated with its original port_id, you may get some bad request exception. - - Which will causing some know issues: + Which will cause some know issues: 1. Updating floating IP extra attributes, for instance description, will unexpectedly disassociate it. This behavior will interrupt the user's service traffic. And this is because that user can submit an empty request dict (without port_id parameter) for the floating IP updating API, and then it will be disassociated by default. 2. If user try to update floating IP extra attribute with port_id that it associated with, the neutron API will return a bad request exception. So there is no way to update the floating IP extra attributes without changing it's association. And there is already a bug for the updating floating IP extra attributes issue: https://bugs.launchpad.net/neutron/+bug/1578523 - This bug will be used to handle the API behavior issues. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1607746 Title: API: floating IP updating issues Status in neutron: New Bug description: Now floating IP can be disassociated via two different API data dict: {'port_id': null} or a dict without `port_id` key. And, floating IP can not be updated with its original port_id, you may get some bad request exception. Which will cause some know issues: 1. Updating floating IP extra attributes, for instance description, will unexpectedly disassociate it. This behavior will interrupt the user's service traffic. And this is because that user can submit an empty request dict (without port_id parameter) for the floating IP updating API, and then it will be disassociated by default. 2. If user try to update floating IP extra attribute with port_id that it associated with, the neutron API will return a bad request exception. So there is no way to update the floating IP extra attributes without changing it's association. And there is already a bug for the updating floating IP extra attributes issue: https://bugs.launchpad.net/neutron/+bug/1578523 This bug will be used to handle the API behavior issues. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1607746/+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