Comment 25 for bug 1359082

Dmitry, there is no possibility of IP conflict to begin with if the L3 agents are deployed normally. In the current Neutron code, routers are only scheduled to one L3 agent. If that L3 agent goes down, there is no automatic moving to a new agent so there is no risk of an IP conflict. The only way there could be a conflict is if two agents were configured with the same hostname so they both received the same RPC messages, which is not what they do by default and Fuel has not configured them to do that either.

The patch I referenced adds the ability to automatically reschedule routers to a new agent if an agent goes down, but that is only available in Juno and is disabled by default.