Bug 1243044 - When taking two of three controller nodes down, pacemaker status is wrong
Summary: When taking two of three controller nodes down, pacemaker status is wrong
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Director
Assignee: chris alfonso
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-14 15:49 UTC by Ben Nemec
Modified: 2016-04-18 07:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-15 17:21:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.