What causes a split-brain scenario when utilizing CloudForms High Availability, and how can it be corrected?

Issue

• A split-brain is a scenario wherein, using high availability, two nodes are effectively deemed as 'primary', instead of the intended relationship of primary and secondary, with one replicating data to the other in preparation of the event of failover. This can cause issues such as duplicated data, inconsistent datasets, or nonfunctional nodes and services in a variety of software systems.
• In Red Hat CloudForms Management Engine, which uses a PostgreSQL database backing all operations, high availability is achieved by utilizing a primary and standby database, using a failover monitor so that if the primary is to fail, the standby will take over primary operations.

How Split-brain Scenarios Can Occur in Red Hat CloudForms Management Engine

• Split-brain in Red Hat CloudForms Management Engine can occur at time of setup or during operation due to a large number of reasons ranging from software failure to human error.