What I so far found if fact that probably keepalived process wasn't started for router in such failed case. It's in logs. e g. here: http://logs.openstack.org/74/640874/2/check/neutron-functional/37e3040/logs/dsvm-functional-logs/neutron.tests.functional.agent.l3.extensions.test_port_forwarding_extension.TestL3AgentFipPortForwardingExtensionDVR.test_dvr_ha_router_failover_without_gw.txt.gz#_2019-03-05_23_36_44_978
"No process started for 01fae686-bdfe-4709-baf4-23a564fdbd11 disable /opt/stack/new/neutron/neutron/agent/linux/external_process.py:118"
What I so far found if fact that probably keepalived process wasn't started for router in such failed case. It's in logs. e g. here: http:// logs.openstack. org/74/ 640874/ 2/check/ neutron- functional/ 37e3040/ logs/dsvm- functional- logs/neutron. tests.functiona l.agent. l3.extensions. test_port_ forwarding_ extension. TestL3AgentFipP ortForwardingEx tensionDVR. test_dvr_ ha_router_ failover_ without_ gw.txt. gz#_2019- 03-05_23_ 36_44_978
"No process started for 01fae686- bdfe-4709- baf4-23a564fdbd 11 disable /opt/stack/ new/neutron/ neutron/ agent/linux/ external_ process. py:118"