The "azure-events-az" resource agent fails during probe operations when cluster node name does not match system hostname

Solution Verified - Updated -

Issue

  • Within the output of pcs status 'Full List of Resources' the azure-events-az resource is reporting as FAILED.

     Full List of Resources:
   * fence_azure        (stonith:fence_azure_arm):       Started node1
   * Clone Set: azure-events-az-clone [health-azure-events]:
      * azure-events-az       (ocf::heartbeat:azure-events-az):        FAILED node1
      * azure-events-az       (ocf::heartbeat:azure-events-az):        FAILED node2

  • There are failed azure-events-az resources and the following event is logged:

    Jan  1 00:00:00 Node1 pacemaker-controld[40423]: notice: azure-events-az _monitor_10000@Node2 output [ crm_attribute: Could not map name=Node1 to a UUID\nocf-exit-reason:object of type 'NoneType' has no len()\n ]

Environment

  • Red Hat Enterprise Linux (RHEL) 8,9 with the High Availability Add-On

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content