networking-calico

Delay of up to 30s before floating IPs are reachable

Bug #1660680 reported by Nell Jerram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-calico
Fix Released
Undecided
Nell Jerram

Bug Description

When a floating IP is created (using the usual Neutron API or CLI calls), it can take up to 30s before networking-calico actually programs the data plane such that that floating IP is reachable.

This is because the programming isn't actually happening until the next resync.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-calico (master)

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

Changed in networking-calico:
assignee: nobody → Neil Jerram (neil-jerram)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-calico (master)

Reviewed: https://review.openstack.org/427277
Committed: https://git.openstack.org/cgit/openstack/networking-calico/commit/?id=21fcc8d8e4a20622e87a7051975316c6bc2e1cff
Submitter: Jenkins
Branch: master

commit 21fcc8d8e4a20622e87a7051975316c6bc2e1cff
Author: Neil Jerram <email address hidden>
Date: Tue Jan 31 16:23:07 2017 +0000

    Intercept floating IP creation (as well as update)

    So that we establish the data path for floating IPs as soon as they are
    created, rather than waiting for the next resync.

    Change-Id: I02fc806454837669629cd0ad6fe4c792a66c436a
    Closes-Bug: #1660680

Changed in networking-calico:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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