[Pacemaker] resource status question

David Vossel dvossel at redhat.com
Wed Jul 31 17:23:36 UTC 2013





----- Original Message -----
> From: "Matthew O'Connor" <matt at ecsorl.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, July 31, 2013 12:08:11 PM
> Subject: [Pacemaker] resource status question
> 
> Hi!
> 
> pacemaker 1.1.10...
> 
> I have an AoEtarget resource that uses a DRBD device as its backing
> store.  I was testing fail-over via fencing when I discovered the
> following: When the failed node is brought back online, the AoEtarget
> resource fails its monitor, reporting "not installed."  From what I can
> tell this is a result of the DRBD resource not yet being started on that
> particular node.  The resource script appears to confirm this:
> 
>     # Does the device we are trying to export exist?
>     if [ ! -e ${OCF_RESKEY_device} ]; then
>         ocf_log error "${OCF_RESKEY_device} does not exist"
>         return $OCF_ERR_INSTALLED
>     fi
> 
> Now, this error report sticks, and when I try to migrate the resource
> from its current node to the node reporting the failure, the migrate
> fails.  Is this failure-to-migrate an expected behavior?  I would assume
> as much, which would mean the resource agent needs to be fixed.  (I'm
> actually working on that fix now - where would I submit a resource agent
> patch?)

Since the monitor failed with (not installed) it wouldn't make sense to allow the resource in question to migrate to a node we know it can't run on.  That seems expected to me.

Make a pull request with your changes and submit the patches to https://github.com/ClusterLabs/resource-agents for review.

Thanks,
-- Vossel


> 
> Thanks!
> 
> --
> Thank you!
>   Matthew O'Connor
>   (GPG Key ID: 55F981C4)
> 
> 
> CONFIDENTIAL NOTICE: The information contained in this electronic message is
> legally privileged, confidential and exempt from disclosure under applicable
> law. It is intended only for the use of the individual or entity named
> above. If the reader of this message is not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> message is strictly prohibited. If you have received this communication in
> error, please notify the sender immediately by return e-mail and delete the
> original message and any copies of it from your computer system. Thank you.
>  
> EXPORT CONTROL WARNING:  This document may contain technical data that is
> subject to the International Traffic in Arms Regulations (ITAR) controls and
> may not be exported or otherwise disclosed to any foreign person or firm,
> whether in the US or abroad, without first complying with all requirements
> of the ITAR, 22 CFR 120-130, including the requirement for obtaining an
> export license if applicable. In addition, this document may contain
> technology that is subject to the Export Administration Regulations (EAR)
> and may not be exported or otherwise disclosed to any non-U.S. person,
> whether in the US or abroad, without first complying with all requirements
> of the EAR, 15 CFR 730-774, including the requirement for obtaining an
> export license if applicable. Violation of these export laws is subject to
> severe criminal penalties.
> 
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 




More information about the Pacemaker mailing list