On 2013-12-06T16:06:09, Patrick Hemmer pacema...@feystorm.net wrote:
Hi Patrick,
For a resource that pacemaker expects to be started, it's an error if it
is found to be stopped. Pacemaker can't tell if it is really cleanly
stopped, or died, or ...
Oh, and I'll quote the OCF spec on this
I have a resource which updates DNS records (Amazon's Route53). When it
performs it's `monitor` action, it can sometimes fail because of issues
with Amazon's API. So I want failures to be ignored for the monitor
action, and so I set `op monitor on-fail=ignore`. However now when the
monitor action
Am Freitag, 6. Dezember 2013, 10:11:07 schrieb Patrick Hemmer:
I have a resource which updates DNS records (Amazon's Route53). When it
performs it's `monitor` action, it can sometimes fail because of issues
with Amazon's API. So I want failures to be ignored for the monitor
action, and so I
*From: *Michael Schwartzkopff m...@sys4.de
*Sent: * 2013-12-06 11:16:17 E
*To: *pacemaker@oss.clusterlabs.org
*Subject: *Re: [Pacemaker] monitor on-fail=ignore not restarting when
resource reported as stopped
Am
On 2013-12-06T11:21:02, Patrick Hemmer pacema...@feystorm.net wrote:
So where is the problem? If the script returns ERROR than pacemaker has
to
acct accordingly.
If the script returns ERROR the `on-fail=ignore` should make it do
nothing. Amazon's API failed, we need to just retry again
*From: *Lars Marowsky-Bree l...@suse.com
*Sent: * 2013-12-06 13:44:53 E
*To: *The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
*Subject: *Re: [Pacemaker] monitor on-fail=ignore not restarting when
*From: *Lars Marowsky-Bree l...@suse.com
*Sent: * 2013-12-06 13:44:53 E
*To: *The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
*Subject: *Re: [Pacemaker] monitor on-fail=ignore not restarting when
