The code https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/pacemaker_wrappers/manifests/rabbitmq.pp#L53-L57 should configure additional monitor action for rabbit primitive, but it didn't:
primitive p_rabbitmq-server ocf:fuel:rabbitmq-server \ op promote interval=0 timeout=120 \ op stop interval=0 timeout=120 \ op start interval=0 timeout=360 \ op notify interval=0 timeout=180 \ op demote interval=0 timeout=120 \ op monitor interval=27 role=Master timeout=60 \ op monitor interval=30 timeout=60 \ params command_timeout="-s KILL" debug=true erlang_cookie=EOKOWXQREETZSHFNTPEY node_port=5673 \ meta failure-timeout=360s migration-threshold=INFINITY
As a result, the bug https://bugs.launchpad.net/fuel/+bug/1458828 have arised again and rabbit@node-1 app remained stopped permanently.
The code /github. com/stackforge/ fuel-library/ blob/master/ deployment/ puppet/ pacemaker_ wrappers/ manifests/ rabbitmq. pp#L53- L57
https:/
should configure additional monitor action for rabbit primitive, but it didn't:
primitive p_rabbitmq-server ocf:fuel: rabbitmq- server \ cookie= EOKOWXQREETZSHF NTPEY node_port=5673 \ timeout= 360s migration- threshold= INFINITY
op promote interval=0 timeout=120 \
op stop interval=0 timeout=120 \
op start interval=0 timeout=360 \
op notify interval=0 timeout=180 \
op demote interval=0 timeout=120 \
op monitor interval=27 role=Master timeout=60 \
op monitor interval=30 timeout=60 \
params command_timeout="-s KILL" debug=true erlang_
meta failure-
As a result, the bug https:/ /bugs.launchpad .net/fuel/ +bug/1458828 have arised again and rabbit@node-1 app remained stopped permanently.