l2-population : update_port --admin_state_up False doesn't remove flooding entries

Bug #1282141 reported by Mathieu Rohon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Mathieu Rohon
Havana
Fix Released
Undecided
Unassigned

Bug Description

I run in multi node setup with ML2, L2-population and Linuxbridge MD, and vxlan TypeDriver.

I create 2 VMs on different nodes. When a port gets down on a node with :
neutron update_port <port_uuid> --admin_state_up False

Unicast fdb entries are correctly removed but from the node that still host a VM of the network, but the broadcast entry is not removed.

Before :
# bridge fdb show dev vxlan-1001
00:00:00:44:44:44 dst 192.168.254.74 self permanent
00:00:00:00:00:00 dst 192.168.254.74 self permanent
52:5a:84:bf:fe:23 vlan 0 permanent

after :
00:00:00:00:00:00 dst 192.168.254.74 self permanent
52:5a:84:bf:fe:23 vlan 0 permanent

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

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

Changed in neutron:
assignee: nobody → Mathieu Rohon (mathieu-rohon)
status: New → In Progress
description: updated
tags: added: havana-backport-potential
tags: added: l2-population
Changed in neutron:
importance: Undecided → Medium
milestone: none → icehouse-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/75037
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=043b4dde00216e71e855ff353e41695e4ed940a9
Submitter: Jenkins
Branch: master

commit 043b4dde00216e71e855ff353e41695e4ed940a9
Author: mathieu-rohon <email address hidden>
Date: Thu Feb 20 10:39:43 2014 +0100

    l2-population : send flooding entries when the last port goes down

    Delete port used to call update_port_down to calculate
    its fdb entries during delete_port_precommit. But during
    the pre-commit, the port is still up, so update_port_down
    acts as if there was still one port on the agent, and
    doesn't add flooding entry in its fdb_entries.

    Closes bug #1282141

    Change-Id: Icedd02f33d999200505950beb9169ae3634e551b

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to neutron (stable/havana)

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/88218

Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-3 → 2014.1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/havana)

Reviewed: https://review.openstack.org/88218
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=65e23799668902ee26fee4b753ddcd2fb37b215d
Submitter: Jenkins
Branch: stable/havana

commit 65e23799668902ee26fee4b753ddcd2fb37b215d
Author: mathieu-rohon <email address hidden>
Date: Thu Feb 20 10:39:43 2014 +0100

    l2-population : send flooding entries when the last port goes down

    Delete port used to call update_port_down to calculate
    its fdb entries during delete_port_precommit. But during
    the pre-commit, the port is still up, so update_port_down
    acts as if there was still one port on the agent, and
    doesn't add flooding entry in its fdb_entries.

    Closes bug #1282141

    Change-Id: Icedd02f33d999200505950beb9169ae3634e551b
    (cherry picked from commit 043b4dde00216e71e855ff353e41695e4ed940a9)

tags: added: in-stable-havana
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.