Pull Errors with azure-events Resource Agent on all Nodes
This document (000019623) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 15
Situation
2020-01-01T00:00:00.000105+00:00 hostname lrmd[2345]: notice: rsc_azure-events_monitor_10000:32032:stderr [ INFO:azure-events:monitor: another node is pulling; retry in 1 seconds ]
2020-01-01T00:00:00.000305+00:00 hostname lrmd[2345]: notice: rsc_azure-events_monitor_10000:32032:stderr [ INFO:azure-events:monitor: another node is pulling; retry in 1 seconds ]
2020-01-01T00:00:00.000505+00:00 hostname lrmd[2345]: notice: rsc_azure-events_monitor_10000:32032:stderr [ WARNING:azure-events:monitor: exceeded maximum number of attempts (3) to pull events ]
Resolution
SLES12 SP3: resource-agents-4.0.1+git.1495055229.643177f1-2.48.2
SLES12 SP4: resource-agents-4.3.018.a7fb5035-3.48.2
SLES12 SP5: resource-agents-4.3.018.a7fb5035-3.48.2
SLES15: resource-agents-4.3.0184.6ee15eb2-3.45.4
SLES15 SP1: resource-agents-4.3.0184.6ee15eb2-4.30.4
SLES15 SP2: resource-agents-4.4.0+git57.70549516-3.3.3
For clusters already in this condition, manually set the attr_globalPullState back to "IDLE" with this command:
hostname:~ # crm_attribute --name azure-events_globalPullState --update IDLE --quiet --type crm_config
Cause
Additional Information
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/scheduled-events
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019623
- Creation Date: 05-May-2020
- Modified Date:04-Aug-2020
-
- SUSE Linux Enterprise High Availability Extension
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com