Raising priority to "High" because this may lead to corosync/pacemaker thinking there are 4 nodes instead of 3 on a fresh deployment, and then we think we have an HA deployment where we are in fact not HA. Again there is a workaround: running the `update-ring` action after deployment.
Raising priority to "High" because this may lead to corosync/pacemaker thinking there are 4 nodes instead of 3 on a fresh deployment, and then we think we have an HA deployment where we are in fact not HA. Again there is a workaround: running the `update-ring` action after deployment.