Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] DRBD Resource Agent flaw when stopping
Date: Wed, 3 Nov 2010 18:24:59 +0100	[thread overview]
Message-ID: <20101103172459.GF4767@barkeeper1-xen.linbit> (raw)
In-Reply-To: <20101103085515.16500maycqm4c2ub@groupware.intern.b1-systems.de>

On Wed, Nov 03, 2010 at 08:55:15AM +0100, Uwe Grawert wrote:
> Hello,
> 
> in the OCF Resource Agent (ocf:linbit:drbd) is a flaw, when cleaning
> up a resource and stopping the resource afterwards. The resource
> agent returns a OCF_ERR_CONFIGURED which happens because of the
> following lines:
> 
> if [[ ${OCF_RESKEY_CRM_meta_notify_start_uname- NOT SET } = " NOT
> SET " ]]; then
> 	ocf_log err "you really should enable notify when using this RA"
> 	return $OCF_ERR_CONFIGURED
> fi
> 
> After a cleanup of a started resource the variable
> OCF_RESKEY_CRM_meta_notify_start_uname is empty. A simple and quick
> solution would be to add "stop" to the following block in a case
> switch:
> 
> case $__OCF_ACTION in
> monitor|validate-all)
> :;;
> 
> This is line 778 in the Resource Agent. In my opinion it does not
> make much sense to make the "is notify enabled" check when stopping
> a resource. Hence it seems reasonable to exclude a stop action from
> this check.
> 
> Is there something that speaks against it? If not, I will send a
> patch to this list.


Thanks,
but that should be fixed already:
http://git.drbd.org/?p=drbd-8.3.git;a=shortlog

Always first check git...

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

      reply	other threads:[~2010-11-03 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  7:55 [Drbd-dev] DRBD Resource Agent flaw when stopping Uwe Grawert
2010-11-03 17:24 ` Lars Ellenberg [this message]

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=20101103172459.GF4767@barkeeper1-xen.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.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