PeerDbDelete was passing the wrong field
The peerDbDelete was passing the wrong field to the underlay Delete operation causing the mac entry to not being deleted from the bridge on the overlay. This caused connectivity issue when a container that before was remote was now scheduled on the local node. The entry was such: bridge fdb show | grep -i 02:42:0a:01:00:02 02:42:0a:01:00:02 dev vxlan0 master br0 02:42:0a:01:00:02 dev vxlan0 dst 172.31.14.63 link-netnsid 0 self permanent That was still pointing to a remove node Signed-off-by: Flavio Crisciani <flavio.crisciani@docker.com>
This commit is contained in:
parent
f5ff00cba7
commit
de9a397ae2
|
@ -254,7 +254,7 @@ func (d *driver) peerOpRoutine(ctx context.Context, ch chan *peerOperation) {
|
|||
case peerOperationADD:
|
||||
err = d.peerAddOp(op.networkID, op.endpointID, op.peerIP, op.peerIPMask, op.peerMac, op.vtepIP, op.updateDB, op.l2Miss, op.l3Miss, op.localPeer)
|
||||
case peerOperationDELETE:
|
||||
err = d.peerDeleteOp(op.networkID, op.endpointID, op.peerIP, op.peerIPMask, op.peerMac, op.vtepIP, op.localPeer)
|
||||
err = d.peerDeleteOp(op.networkID, op.endpointID, op.peerIP, op.peerIPMask, op.peerMac, op.vtepIP, op.updateDB)
|
||||
}
|
||||
if err != nil {
|
||||
logrus.Warnf("Peer operation failed:%s op:%v", err, op)
|
||||
|
|
Loading…
Reference in New Issue