Comment 6 for bug 1531013

Kevin,

I can replicate this issue to a certain extent by firing up hundreds of instances in dozens of networks across multiple (dozens/hundreds) of compute nodes. In most cases, I see duplicates of the flooding entries (about 2 per network per vtep). In the environment this bug was opened for, I see thousands of duplicates. That number fluctuates wildly though. Last test, there were ~15 million total FDB entries on a single network node (mainly duplicates).

I did try appending to the FDB table manually using an existing vxlan interface and some bogus VTEPs using the following:

for i in {1..10}; do for x in {1..20}; do bridge fdb append 00:00:00:00:00:00 dev vxlan-36 dst 172.29.$i.$x; done; done

That should create about 200 entries. At some point in that loop, the 'bridge fdb show' output would just begin looping forever. YMMV. This may not be a valid test, but it does cause some wonky behavior regardless and has been verified on CentOS and Ubuntu. This 'test' is probably more reproducible by bumping up the numbers from 200 to say, 2000.