From: Uwe Grawert <grawert@b1-systems.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] DRBD Resource Agent flaw when stopping
Date: Wed, 03 Nov 2010 08:55:15 +0100 [thread overview]
Message-ID: <20101103085515.16500maycqm4c2ub@groupware.intern.b1-systems.de> (raw)
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.
--
Uwe Grawert
Linux / Unix Consultant & Trainer
Tel.: +49 151 12051100
Mail: grawert@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
next reply other threads:[~2010-11-03 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 7:55 Uwe Grawert [this message]
2010-11-03 17:24 ` [Drbd-dev] DRBD Resource Agent flaw when stopping Lars Ellenberg
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=20101103085515.16500maycqm4c2ub@groupware.intern.b1-systems.de \
--to=grawert@b1-systems.de \
--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