Comment 6 for bug 1580648

I've faced this problem on a production cluster twice in a few weeks, so setting the bug status back to 'confirmed'.

2 L3 agents were 'active' for the routers, and 1 inactive (3 nodes setup).