W/o this fix, the timeout command is used with rabbitmqctl
wrapper, which uses a 'su' when invoked as not a rabbitmq user.
This is an issue as the 'su' changes the original
process group. And if the timeout command expired, it would kill
only processes in this original process group, leaving orphaned
commands what do not belong to whis group anymore.
The solution is to issue all timeout wrapped rabbitmqctl commands
as the rabbitmq user in the OCF script
Reviewed: https:/ /review. openstack. org/179748 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=6826b0cd7c9 e48888f92b8bcac 94a733ff609f29
Committed: https:/
Submitter: Jenkins
Branch: stable/5.1
commit 6826b0cd7c9e488 88f92b8bcac94a7 33ff609f29
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Apr 20 17:42:41 2015 +0200
Fix RabbitMQ ocf_run with the timeout command.
W/o this fix, the timeout command is used with rabbitmqctl
wrapper, which uses a 'su' when invoked as not a rabbitmq user.
This is an issue as the 'su' changes the original
process group. And if the timeout command expired, it would kill
only processes in this original process group, leaving orphaned
commands what do not belong to whis group anymore.
The solution is to issue all timeout wrapped rabbitmqctl commands
as the rabbitmq user in the OCF script
Closes-bug: #1446241
Change-Id: I139255237fd34b 555f248cb826deb 13b7e134e8d 3c84cd780dcf1ad 10933f4955)
Signed-off-by: Bogdan Dobrelya <email address hidden>
(cherry picked from commit b725527d92c3137