Comment 2 for bug 1933196

I was already suspicious of the node1 setting, but the comment from Olivier makes it clear in my mind that this is related to bug #1874719.

The hacluster charm has a fix to address this, which should resolve this for new deployments. However, existing deployments will need to be cleaned up using the above workaround from comment #1.

I'll add charm-hacluster and mark it as invalid for charm-masakari as it is due to functionality in the hacluster charm. This may be marked as a duplicate to the above bug as well, but I'll leave that momentarily for later while we determine if clones should be set to the number of nodes determined in pacemaker (my default answer is yes) or the number of units that exist in the deployment.