floating-ip update does not take effect

Bug #1645829 reported by Deepak Agrawal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenContrail
New
Undecided
Anuradha

Bug Description

We are trying to disassociating a floating-ip from a VM. We call contrail-API to update "floating-ip" with VNI as Null. Though, contrail API server returns 200, this does not take effect on MX where we checked the route. Route is still pointing to compute VM. Following is snip of API which fails to update floating-ip

contrail-api-0-stdout.log:INFO:vpc-ctrl1:contrail-api:Config:0:__default__ [SYS_INFO]: VncApiConfigLog: api_log
 = << identifier_uuid = 901bec08-6452-4343-8aa3-0e41202cab9d <snIP>
771L, u'uuid_lslong': 9989844071313353629L}}, 'floating_ip_fixed_ip_address': None, 'uuid': '901bec08-6452-4343
-8aa3-0e41202cab9d', 'virtual_machine_interface_refs': []}} domain = default-domain >>
contrail-api-0-stdout.log:127.0.0.1 - - [2016-11-29 13:33:06] "PUT /floating-ip/901bec08-6452-4343-8aa3-0e41202
cab9d HTTP/1.1" 200 256 0.009325

Returned 200 but /32 route on MX for this floating-ip is still intact in BGP. Don't see any error in if-map server etc..

Any pointers how to debug this problem ? we are using contrail 2.2.0

Anuradha (anu05sh)
Changed in opencontrail:
assignee: nobody → Anuradha (anu05sh)
Revision history for this message
Anuradha (anu05sh) wrote :

floating ip disassociate working in the latest version

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.