Comment 1 for bug 1933196

To be more precise, the issue is not exactly related to an association with the compute nodes.
It is indirectly related to issue #1874719 where at the initialization of Corosync takes in account the non-existing node "node1"

Looking at the code here : https://github.com/openstack/charm-hacluster/blob/bbe25222e0ad91ba83f2d5f5c72ac8889482575c/hooks/utils.py#L981

It sets the option clone-max to 4 at initialization which correspond to :
- node1 + 3 units of Masakari.
However since node1 is unavailable, it tries to run the resource on any other available node.

Another quicker workaround is to run this command (and in fact what the mentioned hook above does) :
juju ssh masakari/leader \
  sudo crm configure set cl_res_masakari_haproxy.clone-max 3

Replace the number 3 by any number of Masakari units there are in the deployment.

An improvement eventually may be to set a location constraint eventually to ensure it doesn't try to run specific resources such as haproxy and vIP on the remote nodes.