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

Bug 1243044

Summary:	When taking two of three controller nodes down, pacemaker status is wrong
Product:	Red Hat OpenStack	Reporter:	Ben Nemec <bnemec>
Component:	rhosp-director	Assignee:	chris alfonso <calfonso>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Director	CC:	hbrock, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-15 17:21:01 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 Ben Nemec 2015-07-14 15:49:54 UTC

Description of problem: If two of three controller nodes in an HA setup are taken down, the pacemaker status does not properly display that the two nodes are down.


Version-Release number of selected component (if applicable): beta 2 code drop


How reproducible: Unsure, only tried it once


Steps to Reproduce:
1. Deploy an overcloud with 3 controllers
2. Stop two of the controllers
3. run pcs status on the remaining controller

Actual results: Pacemaker shows for some services that only one node is down, with the other two up.  It properly stops the VIPs however, since quorum has been lost in this case and nothing will work.


Expected results: Services are not expected to work in this situation, but it would be expected that pcs status properly shows the two down nodes.


Additional info:

Comment 3 chris alfonso 2015-07-15 17:21:01 UTC

Once you take 2 of 3 controllers out, the cluster is invalid and not recoverable.