The action_stop may sometimes stop the rabbitmq-server gracefully
by the PID, but leave unresponsive beam.smp processes running and
spoiling rabbits. Those shall be stopped as well. The solution is:
- make proc_stop() to accept a pid=none to use a name matching instead
- make kill_rmq_and_remove_pid() to stop by the beam process matching as well
- fix stop_server_process() to ensure there is no beam process left running
Reviewed: https:/ /review. openstack. org/276201 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=d3b77ffa158 1145015726255c9 56d937c2b273e2
Committed: https:/
Submitter: Jenkins
Branch: stable/8.0
commit d3b77ffa1581145 015726255c956d9 37c2b273e2
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Feb 4 11:57:28 2016 +0100
Fix action_stop for the rabbit OCF
The action_stop may sometimes stop the rabbitmq-server gracefully and_remove_ pid() to stop by the beam process matching as well process( ) to ensure there is no beam process left running
by the PID, but leave unresponsive beam.smp processes running and
spoiling rabbits. Those shall be stopped as well. The solution is:
- make proc_stop() to accept a pid=none to use a name matching instead
- make kill_rmq_
- fix stop_server_
Closes-bug: #1541029
Change-Id: Ib9669d15bb714b e8a88fd65d7f181 5173da788d3
Signed-off-by: Bogdan Dobrelya <email address hidden>