pacemaker rsc_azure-events unknown error with corosync hostname change

[schemert15]

We are switching our pacemaker cluster on SLES from 2 to 3 subnets. On the new subnet, the cluster corosync traffic needs to flow. We changed corosync.conf. The application resources come up, but azure-events goes into error.

message:

-rsc_azure-events_monitor_120000:86 [ Could not map name= to a UUID\nocf-exit-reason:object of type 'NoneType' has no len()\n ]

is not the hostname of the vm.

is there a way to fix this?

Thanks, Sander

[oalbrigt]

Sounds like the following issue, or similar: https://stackoverflow.com/questions/52812899/could-not-map-name-uuid-pacemaker-linux-clustering