yahoo-eng-team team mailing list archive

[Mathieu Rohon <mathieu.rohon@xxxxxxxxx>]

Public bug reported:

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

I creat 2 VM on different node. 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, 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

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: ml2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1282141

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

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I run in multi node setup with ML2, L2-population and Linuxbridge MD,
  ad vxlan TD.

  I creat 2 VM on different node. 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, 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1282141/+subscriptions