Both checks heartbeat_crm and heartbeat_crm.resources nailed down the resources / DC to
the node which held the resources / DC during inventory. This was not fitting most users
requirements and has been changed. By default the node currently holding the resources / DC
does not matter anymore as long as they are held by at least one node.
If you like to change this behaviour back to the old default, you need to configure the
inventory rule Heartbeat CRM Inventory and re-run an inventory on the affected
Already inventorized checks should continue working as they did before. The change only
affects newly inventorized services.
Two new WATO rules Heartbeat CRM general status and Heartbeat CRM resource status
have been added to make the parameters of these checks configurable.
To the list of all Werks