From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] When is fencing considered successful?
Date: Wed, 29 Oct 2008 11:22:22 -0500 [thread overview]
Message-ID: <20081029162221.GC23927@redhat.com> (raw)
In-Reply-To: <1225296761.4239.31.camel@dhcp80-204.msp.redhat.com>
On Wed, Oct 29, 2008 at 11:12:41AM -0500, Kevin Anderson wrote:
> Hi all,
>
> Recently we had cluster customer where the fencing agent successfully
> powered off a node, but the script failed to power the node back on due
> to firmware changes on the fencing device.
>
> Question is whether we should consider this a successful fence event or
> does the agent have to complete everything? The primary purpose of the
> fencing agent is to stop the node from participating in the cluster. In
> this case, that was successful. But, because the power on attempt
> failed, the fence agent reported failure and the cluster hung waiting
> for a followup action.
>
> It would seem to me that the fence agent should report success in this
> case, and maybe post a warning message about the failure to power on.
>
> Thoughts?
Definately
next prev parent reply other threads:[~2008-10-29 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 16:12 [Cluster-devel] When is fencing considered successful? Kevin Anderson
2008-10-29 16:22 ` David Teigland [this message]
2008-10-31 19:44 ` Kevin Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081029162221.GC23927@redhat.com \
--to=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).