Comment 18 for bug 1625305

@Esha,

Do you have a way to reproduce this? Unfortunately the issue occurred at some other point that corrupted the state (by giving the same vlan to two different networks). Were you running two copies of the L2 agent?