← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1799135] [NEW] [l3][port_forwarding] update floating IP (has binding port_forwarding) with empty {} input will lose router_id

 

Public bug reported:

ENV: devstack master

Step to reproduce:
1. create floating IP
2. create port forwarding for that floating IP
3. update floating IP with empty dict:
curl -g -i -X PUT http://controller:9696/v2.0/floatingips/2bb4cc5d-7fae-4c1b-9482-ead60d67abea \
-H "User-Agent: python-neutronclient" -H "Accept: application/json" \
-H "X-Auth-Token: <token>" \
-d '{"floatingip": {}}'

Then this floating IP will turn to a bad status, it can not be managed
anymore. Every action on this floating IP will get a neutron-server
ERROR log.

Furturemore only updating floating IP qos_policy_id can also result such behavior.
curl -g -i -X PUT http://controller:9696/v2.0/floatingips/2bb4cc5d-7fae-4c1b-9482-ead60d67abea \
-H "User-Agent: python-neutronclient" -H "Accept: application/json" \
-H "X-Auth-Token: <token>" \
-d '{"floatingip": {"qos_policy_id": "d9d3639e-b616-4007-a8fe-52d6154f1eec"}}'

** 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/1799135

Title:
  [l3][port_forwarding] update floating IP (has binding port_forwarding)
  with empty {} input will lose router_id

Status in neutron:
  New

Bug description:
  ENV: devstack master

  Step to reproduce:
  1. create floating IP
  2. create port forwarding for that floating IP
  3. update floating IP with empty dict:
  curl -g -i -X PUT http://controller:9696/v2.0/floatingips/2bb4cc5d-7fae-4c1b-9482-ead60d67abea \
  -H "User-Agent: python-neutronclient" -H "Accept: application/json" \
  -H "X-Auth-Token: <token>" \
  -d '{"floatingip": {}}'

  Then this floating IP will turn to a bad status, it can not be managed
  anymore. Every action on this floating IP will get a neutron-server
  ERROR log.

  Furturemore only updating floating IP qos_policy_id can also result such behavior.
  curl -g -i -X PUT http://controller:9696/v2.0/floatingips/2bb4cc5d-7fae-4c1b-9482-ead60d67abea \
  -H "User-Agent: python-neutronclient" -H "Accept: application/json" \
  -H "X-Auth-Token: <token>" \
  -d '{"floatingip": {"qos_policy_id": "d9d3639e-b616-4007-a8fe-52d6154f1eec"}}'

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


Follow ups