QA code is okay. Router didn't stick to agent on failed env.
After looking into logs it shows that at time when router was created there were no l3 agents alive - so it wasn't scheduling to some. Why router didn't scheduling after that - it is a question. I suppose that it is can be a bug in neutron itself. So I move this bug to neutron team - if there will be no root cause found, we will try to create a workaround solution.
QA code is okay. Router didn't stick to agent on failed env.
After looking into logs it shows that at time when router was created there were no l3 agents alive - so it wasn't scheduling to some. Why router didn't scheduling after that - it is a question. I suppose that it is can be a bug in neutron itself. So I move this bug to neutron team - if there will be no root cause found, we will try to create a workaround solution.