yahoo-eng-team team mailing list archive

[OpenStack Infra <1578523@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/351477
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ab302fe6cde3795cc778179fdcadf71a188829b5
Submitter: Jenkins
Branch:    master

commit ab302fe6cde3795cc778179fdcadf71a188829b5
Author: LIU Yulong <liuyulong@xxxxxx>
Date:   Fri Aug 5 11:24:20 2016 +0800

    Correct floating IP updating with same port_id issue
    
    If user try to update floating IP with port_id that it associated
    with, the neutron API will return a bad request exception.
    
    This patch adds a check for the updating API to determine whether
    the association is changed.
    
    Change-Id: I620b085238cb27dcef9989a27ba14cd2e3f5f07c
    Closes-Bug: #1578523


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1578523

Title:
  Update associated Floating IP returns Conflict even when there is no
  actual change

Status in neutron:
  Fix Released

Bug description:
  This is inaccurate that floating IP has nothing changed but we get an
  NeutronError.

  How to reproduce:

  Update floating IP that already associated to a (same) port.

  step 1: Associate
  neutron --debug floatingip-associate cd3b0496-bd2e-48a8-8706-48d4c4d85c44 303af774-b12f-462e-a38a-1c616b6cc335

  step 2: Update floating IP with same port_id again
  curl -g -i -X PUT http://controller:9696/v2.0/floatingips/cd3b0496-bd2e-48a8-8706-48d4c4d85c44.json -H \
  "User-Agent: python-neutronclient" -H "Content-Type: application/json" -H "Accept: application/json" \
  -H "X-Auth-Token: 531460c39c1744d1b5b83b6f20fc74a2" -d '{"floatingip": {"port_id": "303af774-b12f-462e-a38a-1c616b6cc335"}}'

  {"NeutronError": {"message": "Cannot associate floating IP
  172.16.5.145 (cd3b0496-bd2e-48a8-8706-48d4c4d85c44) with port 303af774
  -b12f-462e-a38a-1c616b6cc335 using fixed IP 192.168.111.48, as that
  fixed IP already has a floating IP on external network
  2cad629d-e523-4b83-90b9-c0cc0ba1250d.", "type":
  "FloatingIPPortAlreadyAssociated", "detail": ""}}

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