Comment 4 for bug 1642613

we've found related issue.

during the failover test with shutdown of the primary controller
we've faced with the next problem:

nova-compute lost connection with rabbit because of default gateway for bg_mgmt is set to 10.109.1.6

auto br-mgmt
iface br-mgmt inet static
bridge_ports enp0s5
address 10.109.1.5/24
gateway 10.109.1.6

root@node-3:~# ip route
default via 10.109.1.6 dev br-mgmt
10.109.0.0/24 dev br-fw-admin proto kernel scope link src 10.109.0.6
10.109.1.0/24 dev br-mgmt proto kernel scope link src 10.109.1.5
10.109.2.0/24 dev br-storage proto kernel scope link src 10.109.2.5
unreachable 169.254.169.254 scope host
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

and neutron-openvswith agent can't up.

the root cause is in the vip__management resource configuration on the new primary controller

primitive vip__management ocf:fuel:ns_IPaddr2 \
        params base_veth=v_management bridge=br-mgmt cidr_netmask=24 gateway=none gateway_metric=0 iflabel=ka ip=10.109.1.7 iptables_comment=undef ns=haproxy ns_iptables_start_rules=undef ns_iptables_stop_rules=undef ns_veth=b_management other_networks=undef \
        meta failure-timeout=60 migration-threshold=3 resource-stickiness=1 target-role=Started \
        op monitor interval=5 timeout=20 trace_ra=1 \
        op start interval=0 timeout=30 trace_ra=1 \
        op stop interval=0 timeout=30 trace_ra=1

When I've changed the default route for the nova-compute node to 10.109.1.7 (configured by pacemaker) and restarted neutron-opevswitch (successfully connected rabbit with 10.109.1.7 as default route) agent - an instance has been created successfully.