Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1628524

Summary:	rabbitmqctl cluster_status returns 0 even when app is stopped, causing pacemaker wrongly reports the state
Product:	Red Hat OpenStack	Reporter:	Chen <cchen>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <plemenko>
Status:	CLOSED DUPLICATE	QA Contact:	Udi Shkalim <ushkalim>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	apevec, jeckersb, lhh, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-13 14:04:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chen 2018-09-13 10:56:51 UTC

Description of problem:

rabbitmqctl cluster_status returns 0 even when app is stopped, causing pacemaker wrongly reports the state

Version-Release number of selected component (if applicable):

OSP13

How reproducible:

100% 

Steps to Reproduce:

1. Set cluster_partition_handling to pause_minority
2. Kill two of the rabbitmq containers
3. Monitor pcs status

Actual results:

The remaining rabbitmq stopped the application, but the pcs status shows the rabbit is still Started because rabbitmqctl cluster_status returns 0.

Expected results:

pcs status should show the remaining rabbit is stopped.

Additional info:

Comment 1 John Eckersberg 2018-09-13 14:04:52 UTC


*** This bug has been marked as a duplicate of bug 1595753 ***