Hybrid bridge should permanently keep MAC entries

Bug #1715317 reported by Sahid Orentino
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Incomplete
Undecided
Unassigned
os-vif
Fix Released
Undecided
Sahid Orentino

Bug Description

The linux bridge installed for the particular vif type ovs-hybrid should be configured to persistently keep the MAC learned from the RARP packets sent by QEMU when starting on destination node. That to avoid any break of the datapath during a live-migration.

That issue can be saying when using the opflex plugin.

  https://github.com/noironetworks/python-opflex-agent/commit/3163b9a2668f29dd1e52e9757b8c25ef48822765

tags: added: ocata-backport-potential
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

Sahid, could you please clarify what steps you have in mind to fix the problem ? When you say "the linux bridge should learn the MAC addresses", you mean the Neutron L2 agent running on the compute nodes, right?

Changed in nova:
status: New → Incomplete
Revision history for this message
Sahid Orentino (sahid-ferdjaoui) wrote :
Changed in os-vif:
assignee: nobody → sahid (sahid-ferdjaoui)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-vif (master)

Reviewed: https://review.openstack.org/501132
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Submitter: Jenkins
Branch: master

commit fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Author: Sahid Orentino Ferdjaoui <email address hidden>
Date: Wed Sep 6 03:35:58 2017 -0400

    ovs-hybrid: should permanently keep MAC entries

    The linux bridge installed for the particular vif type ovs-hybrid
    should be configured to persistently keep the MAC learned from the
    RARP packets sent by QEMU when starting on destination node. That to
    avoid any break of the datapath during a live-migration. That because
    at some point of the live-migration source and destination can be on
    a same L2 and we could have the destination bridge learning from source.

    Change-Id: I50775df3629a079e6ba6f167ebfa499ffa5c7cac
    Closes-Bug: 1715317
    Related-Bug: 1414559

Changed in os-vif:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-vif (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/505731

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-vif 1.8.0

This issue was fixed in the openstack/os-vif 1.8.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-vif (stable/pike)

Reviewed: https://review.openstack.org/505731
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=4d108c1c8f4ea9c147c4cac59fe9ecebf73e3bd7
Submitter: Zuul
Branch: stable/pike

commit 4d108c1c8f4ea9c147c4cac59fe9ecebf73e3bd7
Author: Sahid Orentino Ferdjaoui <email address hidden>
Date: Wed Sep 6 03:35:58 2017 -0400

    ovs-hybrid: should permanently keep MAC entries

    The linux bridge installed for the particular vif type ovs-hybrid
    should be configured to persistently keep the MAC learned from the
    RARP packets sent by QEMU when starting on destination node. That to
    avoid any break of the datapath during a live-migration. That because
    at some point of the live-migration source and destination can be on
    a same L2 and we could have the destination bridge learning from source.

    Change-Id: I50775df3629a079e6ba6f167ebfa499ffa5c7cac
    Closes-Bug: 1715317
    Related-Bug: 1414559
    (cherry picked from commit fa4ff64b86e6e1b6399f7250eadbee9775c22d32)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-vif 1.7.1

This issue was fixed in the openstack/os-vif 1.7.1 release.

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.