we fix this issue by add the neutron-gateway hostname in /etc/hosts:
<management ip> neutron-gateway
Try testing with the following procedure to see if you have the problem to bring up the pacemaker
1. on the active node (node 1), stop pacemaker - hostname will be still neutron-gateway
2. the passive node (node 2) becomes the active node - hostname will be changed to neutron-gateway
3. go back to the node 1 and start pacemaker - same hostname will bring trouble to start the pacemaker
while it could be fixed manually by changing the node 1 hostname back.
we fix this issue by add the neutron-gateway hostname in /etc/hosts:
<management ip> neutron-gateway
Try testing with the following procedure to see if you have the problem to bring up the pacemaker
1. on the active node (node 1), stop pacemaker - hostname will be still neutron-gateway
2. the passive node (node 2) becomes the active node - hostname will be changed to neutron-gateway
3. go back to the node 1 and start pacemaker - same hostname will bring trouble to start the pacemaker
while it could be fixed manually by changing the node 1 hostname back.