-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-8.8.0
-
resource-agents-4.10.0-67.el9
-
None
-
Moderate
-
rhel-ha
-
13
-
17
-
5
-
QE ack
-
False
-
False
-
-
None
-
None
-
Pass
-
None
-
None
What were you trying to do that didn't work?
Current version of azure-events-az resource agent does not have a retry logic in case the Azure IMDS endpoint is unresponsible. Thsi can lead to agent failures.
Please provide the package NVR for which bug is seen:
Asking for changes as of commit 7739c2a802c1dddb6757ff75cf7f6582a89bd518 https://github.com/ClusterLabs/resource-agents/blob/7739c2a802c1dddb6757ff75cf7f6582a89bd518/heartbeat/azure-events-az.in to be provided in update for resource-agents.
How reproducible:
Unavailable IMDS endpoint 169.254.169.254 from VM running resource agent. TCP timeout or http error will lead to errors in agent.
With changes made azure-events-az and merged in upstream repo, retry logic will prevent issues and potential support requests as configurable wait time and retry attempts are done before declaring resource agent as failed.
- links to
-
RHBA-2025:144883 resource-agents bug fix and enhancement update