Monitor operation for the stonith resource using stonith agent fence_azure_arm gets timed out with error : "ReadTimeoutError" and "ProtocolError"

Solution Verified - Updated -

Issue

  • Stonith agent fence_azure_arm reports following error messages, prior to the monitor operation timeout of the stonith resource :

    Dec  9 16:37:59 node1 /fence_azure_arm[1215009]: Retrying (Retry(total=3, connect=4, read=3, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))': /subscriptions/*****-****-****-*****-********/resourceGroups/resourceGroup-RG/providers/Microsoft.Compute/virtualMachines?api-version=2019-03-01
    Dec  9 16:38:03 node1 /fence_azure_arm[1215009]: Retrying (Retry(total=2, connect=4, read=2, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))': /subscriptions/*****-****-****-*****-********/resourceGroups/resourceGroup-RG/providers/Microsoft.Compute/virtualMachines?api-version=2019-03-01
    Dec  9 16:38:18 node1 pacemaker-fenced[21590]: notice: Operation 'monitor' [1215009] using azure_fence_tst could not be executed: Timed Out (Fence agent did not complete within 2m)
    Dec  9 16:38:18 node1 pacemaker-controld[21594]: error: Result of monitor operation for azure_fence_tst on node1: Timed Out after 2m (Fence agent did not complete within 2m)
    
    
    
    Dec  9 16:40:35 node1 /fence_azure_arm[1221173]: Retrying (Retry(total=3, connect=4, read=3, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='management.azure.com', port=443): Read timed out. (read timeout=100)",)': /subscriptions/*****-****-****-*****-********/resourceGroups/resourceGroup-RG/providers/Microsoft.Compute/virtualMachines?api-version=2019-03-01
    Dec  9 16:40:54 node1 pacemaker-fenced[21590]: warning: fence_azure_arm[1221173] stderr: [ 2024-12-09 16:40:35,424 WARNING: Retrying (Retry(total=3, connect=4, read=3, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='management.azure.com', port=443): Read timed out. (read timeout=100)",)': /subscriptions/*****-****-****-*****-********/resourceGroups/resourceGroup-RG/providers/Microsoft.Compute/virtualMachines?api-version=2019-03-01 ]
    Dec  9 16:40:54 node1 pacemaker-fenced[21590]: notice: Operation 'monitor' [1221173] using azure_fence_tst could not be executed: Timed Out (Fence agent did not complete within 2m)
    Dec  9 16:40:54 node1 pacemaker-controld[21594]: error: Result of monitor operation for azure_fence_tst on node1: Timed Out after 2m (Fence agent did not complete within 2m)
    

Environment

  • Red Hat Enterprise Linux Server 7,8 or 9 (with the High Availability Add-on)
  • Pacemaker
  • fence_azure_arm
  • Microsoft Azure VMs as cluster members

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