# Revision history [back]

Just a guess regarding your issue :-
Report above :-

[root@overcloud-controller-1 log]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: overcloud-controller-1 (version 1.1.15-11.el7_3.2-e174ec8) - partition with quorum
Last updated: Wed Mar  1 06:01:15 2017          Last change: Wed Mar  1 05:50:30 2017 by hacluster via crmd on    overcloud-controller-0


However,

In case when  quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a majority of quorum votes necessary to run services, and thus it is unable to take over any resources.


UPDATE 03/01/17 19:41 MSK
Quoting http://stackoverflow.com/questions/23236871/what-is-the-defined-behavior-of-a-3-node-galera-cluster-after-one-node-dies

The main reason that three servers is the recommended minimum is to increase the chance that a quorum will exist in the event of a network problem. If a cluster has two nodes (or more generally any even number of nodes) a single network link failure could cause the cluster to pause since it could create two partitions with half of the nodes, neither having a quorum. An odd number of nodes means that a single network link failure cannot cause the cluster to pause since there will always be quorum. If there is more than one network link failure, however, things can get more complicated but only a partition with a quorum will function normally.


END UPDATE

Just a guess regarding your issue :-
Report above :-

[root@overcloud-controller-1 log]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: overcloud-controller-1 (version 1.1.15-11.el7_3.2-e174ec8) - partition with quorum
Last updated: Wed Mar  1 06:01:15 2017          Last change: Wed Mar  1 05:50:30 2017 by hacluster via crmd on    overcloud-controller-0


However,

In case when  quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a majority of quorum votes necessary to run services, and thus it is unable to take over any resources.


UPDATE 03/01/17 19:41 MSK
Quoting http://stackoverflow.com/questions/23236871/what-is-the-defined-behavior-of-a-3-node-galera-cluster-after-one-node-dies

The main reason that three servers is the recommended minimum is to increase the chance that a quorum will exist in the event of a network problem. If a cluster has two nodes (or more generally any even number of nodes) a single network link failure could cause the cluster to pause since it could create two partitions with half of the nodes, neither having a quorum. An odd number of nodes means that a single network link failure cannot cause the cluster to pause since there will always be quorum. If there is more than one network link failure, however, things can get more complicated but only a partition with a quorum will function normally.


END UPDATE

Just a guess regarding your issue :-
Report above :-

[root@overcloud-controller-1 log]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: overcloud-controller-1 (version 1.1.15-11.el7_3.2-e174ec8) - partition with quorum
Last updated: Wed Mar  1 06:01:15 2017          Last change: Wed Mar  1 05:50:30 2017 by hacluster via crmd on    overcloud-controller-0


However,

In case when  quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a majority of quorum votes necessary to run services, and thus it is unable to take over any resources.


UPDATE 03/01/17 19:41 MSK
Quoting http://stackoverflow.com/questions/23236871/what-is-the-defined-behavior-of-a-3-node-galera-cluster-after-one-node-dies

The main reason that three servers is the recommended minimum is to increase the chance that a quorum will exist in the event of a network problem. If a cluster has two nodes (or more generally any even number of nodes) a single network link failure could cause the cluster to pause since it could create two partitions with half of the nodes, neither having a quorum. An odd number of nodes means that a single network link failure cannot cause the cluster to pause since there will always be quorum. If there is more than one network link failure, however, things can get more complicated but only a partition with a quorum will function normally.


END UPDATE

Just a guess regarding your issue :-
Report above :-

[root@overcloud-controller-1 log]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: overcloud-controller-1 (version 1.1.15-11.el7_3.2-e174ec8) - partition with quorum
Last updated: Wed Mar  1 06:01:15 2017          Last change: Wed Mar  1 05:50:30 2017 by hacluster via crmd on    overcloud-controller-0


However,

In case when  quorum enforcement is enabled, and one of the two nodes fails, then the remaining node can not establish a majority of quorum votes necessary to run services, and thus it is unable to take over any resources.