f8fe5a2fcd
If there are already ongoing actions for a process managed by monit, the module would exit unsuccessfully. It could also give off false positives because it did not determine whether the service was started/stopped when it was in a pending state. Which might be turning the service off, but the action was to start it. For example "Running - pending stop" would be regarded as the service running and "state=enabled" would do nothing. This will make Ansible wait for the state to finalize, or a timeout decided by the new `max_retries` option, before it decides what to do. This fixes issue #244. |
||
---|---|---|
.. | ||
__init__.py | ||
airbrake_deployment.py | ||
bigpanda.py | ||
boundary_meter.py | ||
circonus_annotation.py | ||
datadog_event.py | ||
datadog_monitor.py | ||
librato_annotation.py | ||
logentries.py | ||
monit.py | ||
nagios.py | ||
newrelic_deployment.py | ||
pagerduty.py | ||
pagerduty_alert.py | ||
pingdom.py | ||
rollbar_deployment.py | ||
sensu_check.py | ||
stackdriver.py | ||
uptimerobot.py | ||
zabbix_group.py | ||
zabbix_host.py | ||
zabbix_hostmacro.py | ||
zabbix_maintenance.py | ||
zabbix_screen.py |