W/o this fix, if there are no apps running and rabbit node is actually
not functioning, get_status() would still report 0 considering the rabbit
resource is running. This is an issue as it may lead to the situations
when the resource reported OK, but in fact, the rabbit node is not a cluster
member.
The solution is to not rely only on which_applications() eval exit code
and test if the kernel app is running. Otherwise consider the pacemaker
resource is "not running" as well.
Reviewed: https:/ /review. openstack. org/175457 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=bc4a7ec8093 db81d8d1de47878 8825e228890b05
Committed: https:/
Submitter: Jenkins
Branch: master
commit bc4a7ec8093db81 d8d1de478788825 e228890b05
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Apr 20 17:31:33 2015 +0200
Fix RabbitMQ apps eval in OCF
W/o this fix, if there are no apps running and rabbit node is actually
not functioning, get_status() would still report 0 considering the rabbit
resource is running. This is an issue as it may lead to the situations
when the resource reported OK, but in fact, the rabbit node is not a cluster
member.
The solution is to not rely only on which_applicati ons() eval exit code
and test if the kernel app is running. Otherwise consider the pacemaker
resource is "not running" as well.
Closes-bug: #1446251
Change-Id: Ia2fcb18abb3d97 7c5fcb26bfdeac8 64b6834f478
Signed-off-by: Bogdan Dobrelya <email address hidden>