Comment 3 for bug 1651982

So, the issue here is that on some slow environments there is a race condition due to which some nodes update their GTID SEQNO during the monitor operation on the other nodes. This leads to marking the node that runs with `--wsrep-new-cluster` option to be marked as a duplicate primary component which in turn makes pacemaker fail and restart the node in question. The proper solution would be to use real master-slave OCF script for galera, which is not possible for already released Mitaka and Newton due to significant update impediments. So the solution is to refactor `check_if_new_cluster` method to raise split-brain error only if there are actually more than one primary component by storing info if the node is primary component in the CIB and counting whether there are more than 1 primary components.