BGP: Failed to withdraw route while dissocating floating IP

Bug #1614866 reported by LIU Yulong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Ryan Tidwell

Bug Description

ENV: stable/mitaka

Reproduce:
1. associate floating IP to VM
2. dissociate floating IP from VM
Then you will find the following trace in neutron-bgp-dragent log:
http://paste.openstack.org/show/561084/

Tags: l3-bgp
LIU Yulong (dragon889)
Changed in neutron:
assignee: nobody → LIU Yulong (dragon889)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-dynamic-routing (master)

Fix proposed to branch: master
Review: https://review.openstack.org/357716

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/357722

Revision history for this message
Ryan Tidwell (ryan-tidwell) wrote :

After looking into this, it seems this stems from a list being passed on an RPC call when a dict should be passed instead. The route will eventually be withdrawn because the BGP agent does a full re-sync every 60 seconds. This issue just makes it so we have to wait for the re-sync to withdraw the route rather than withdrawing it immediately.

LIU Yulong (dragon889)
tags: added: l3-bgp
Changed in neutron:
importance: Undecided → High
Revision history for this message
LIU Yulong (dragon889) wrote :

@Ryan,
Assuming that we have 3 DR agent to advertise route to 1 physical router. Each DR agent set the periodic_interval to 60s. Then the withdraw procedure may have duration from 60s to 180s.

Changed in neutron:
assignee: LIU Yulong (dragon889) → Ryan Tidwell (ryan-tidwell)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-dynamic-routing (master)

Reviewed: https://review.openstack.org/357716
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=d92b1e723e47633a4d85562b66a38a916cef6ef9
Submitter: Jenkins
Branch: master

commit d92b1e723e47633a4d85562b66a38a916cef6ef9
Author: LIU Yulong <email address hidden>
Date: Fri Aug 19 16:16:48 2016 +0800

    Gracefully withdraw the floating IP bgp route

    This patch will let the bgp plugin do the floating IP next hop query,
    when floating IP is associated to a port.
    And when a floating IP is dissociated, it will get a route entry with
    `None` next hop for DR agent to withdraw.

    Closes-Bug: #1614866
    Change-Id: I67efa68bb8d115378dd99cb149d60f2b75659c1a

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-dynamic-routing 10.0.0.0b3

This issue was fixed in the openstack/neutron-dynamic-routing 10.0.0.0b3 development milestone.

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.