Comment 3 for bug 1754695

Revision history for this message
Piotr Misiak (piotr-misiak) wrote :

Hi Brian,

We haven't tested this issue on Queens and master.
Currently we are focusing on Pike version, because we need this working on Pike.
This is a cloud with 38 compute nodes and 3 controllers.
When we deploy 100 VMs at once there is usually problem on one or two compute nodes and non of VMs spawned on those compute nodes have network connectivity. Which is obvious because this table entry is common for all VMs connected to particular private network on particular compute node.

After extensive debugging I suppose now that it is more like lack of Vxlan port existence in br-tun than issue with this table entry. I suppose this table entry isn't complete because there are no Vxlan ports configured to controller nodes in br_tun bridge.