On Wed, Mar 28, 2012 at 5:07 PM, Brian J. Murrell wrote:
> On 12-03-28 10:39 AM, Florian Haas wrote:
>>
>> Probably because your resource agent reports OCF_SUCCESS on a probe
>> operation
>
> To be clear, is this the "status" $OP in the agent?
Nope, monitor. Of course, in your implementation moni
On 12-03-28 10:39 AM, Florian Haas wrote:
>
> Probably because your resource agent reports OCF_SUCCESS on a probe
> operation
To be clear, is this the "status" $OP in the agent?
Cheers,
b.
signature.asc
Description: OpenPGP digital signature
___
Pac
On 03/28/2012 04:39 PM, Florian Haas wrote:
[...]
Clearly this resource is not running on all nodes, so why is it
being reported as such?
Probably because your resource agent reports OCF_SUCCESS on a probe
operation when it ought to be returning OCF_NOT_RUNNING. Pastebin the
source of ocf:hydra
On Wed, Mar 28, 2012 at 4:26 PM, Brian J. Murrell wrote:
> We seem to have occasion where we find crm_resource reporting that a
> resource is running on more (usually all!) nodes when we query right
> after adding it:
>
> # crm_resource -resource chalkfs-OST_3 --locate
> resource chalkfs-OST00
We seem to have occasion where we find crm_resource reporting that a
resource is running on more (usually all!) nodes when we query right
after adding it:
# crm_resource -resource chalkfs-OST_3 --locate
resource chalkfs-OST_3 is running on: chalk02
resource chalkfs-OST_3 is running on
