Fix RabbitMQ OCF stop action when no PIDFILE exists
W/o this patch, RabbitMQ OCF action stop would fail
if there is no pid file exist. This is an issue as that
could leave the beam process running and uncontrolled
by the Pacemaker resource agent.
The solution is to invoke 'rabbitmqctl stop' and return generic
error only if this operation have failed as well or timed out.
For this case, there also should be a note provided in logs about
additional manual stop actions required.
Reviewed: https:/ /review. openstack. org/175785 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=bd6470d1683 b777c9980fbb23b e5dcfcf108707e
Committed: https:/
Submitter: Jenkins
Branch: master
commit bd6470d1683b777 c9980fbb23be5dc fcf108707e
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Apr 21 11:24:18 2015 +0200
Fix RabbitMQ OCF stop action when no PIDFILE exists
W/o this patch, RabbitMQ OCF action stop would fail
if there is no pid file exist. This is an issue as that
could leave the beam process running and uncontrolled
by the Pacemaker resource agent.
The solution is to invoke 'rabbitmqctl stop' and return generic
error only if this operation have failed as well or timed out.
For this case, there also should be a note provided in logs about
additional manual stop actions required.
Closes-bug: #1446526
Change-Id: I86272230bd7f0e f8412ccaeb6bbb5 dcaa18387bc
Signed-off-by: Bogdan Dobrelya <email address hidden>