We elaborated newer fix that fixes race condition in apply_changes method and generates xml patch based on the old version of CIB that could not be modified by the other node.
Nevertheless, we found that this bug happens rarely (~3%) of deployments when user deploys 5 controllers and thus 4 of them are deployed in parallel. In this case, the workaround is to check location constraints for vip__public|management resources and add them for missing nodes. Also, another workaround is to deploy controllers in portions of not more than 2 nodes in parallel.
We elaborated newer fix that fixes race condition in apply_changes method and generates xml patch based on the old version of CIB that could not be modified by the other node.
Nevertheless, we found that this bug happens rarely (~3%) of deployments when user deploys 5 controllers and thus 4 of them are deployed in parallel. In this case, the workaround is to check location constraints for vip__public| management resources and add them for missing nodes. Also, another workaround is to deploy controllers in portions of not more than 2 nodes in parallel.