SYMC: Incorrect error code for FIP disassociate

Bug #1517669 reported by Rudrajit Tapadar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
New
Medium
Rudra Rugge
OpenContrail
New
Medium
Rudra Rugge

Bug Description

When a FIP is disassociated from a VIP's port, it always throws 404, even though it has successfully disassociated the port.

Steps to reproduce:
neutron floatingip-associate <fip-uuid> <vip-port-uuid>
neutron floatingip-disassociate <fip-uuid>

Error: Port Not Found

Changed in juniperopenstack:
importance: Undecided → Medium
Changed in opencontrail:
importance: Undecided → Medium
Changed in juniperopenstack:
assignee: nobody → Prakash Bailkeri (prakashmb)
Changed in opencontrail:
assignee: nobody → Prakash Bailkeri (prakashmb)
tags: added: config neutronapi
Changed in juniperopenstack:
assignee: Prakash Bailkeri (prakashmb) → Rudra Rugge (rudrarugge)
Changed in opencontrail:
assignee: Prakash Bailkeri (prakashmb) → Rudra Rugge (rudrarugge)
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.