<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, All!<br>
<br>
On one of my clusters I have resources groups, second group depends
on first resource in the first group. Today I needed to restart one
service from the first group (no dependancies other than group), so
I made in unmanaged:<br>
<br>
May 23 14:14:22 kennedy cib[20888]: notice: cib:diff:
-- <nvpair value="true"
id="wcs_wcsd-meta_attributes-is-managed" /><br>
May 23 14:14:22 kennedy cib[20888]: notice: cib:diff:
++ <nvpair id="wcs_wcsd-meta_attributes-is-managed"
name="is-manage" value="false" /><br>
<br>
I made sure that the resource is "unmanaged" in crm_mon. After that
I stopped the resource.<br>
However, after that the monitor operation was performed and resource
was marked as failed, and both groups got stopped! Well, the second
group got stopped because of dependancy, but why was the first group
stopped because of failure of an unmanaged resource, in the first
place?<br>
<br>
May 23 14:16:32 kennedy crmd[1787]: notice: process_lrm_event: LRM
operation wcs_wcsd_monitor_15000 (call=832, rc=7, cib-update=668,
confirmed=false) not running<br>
May 23 14:16:32 kennedy crmd[1787]: warning: update_failcount:
Updating failcount for wcs_wcsd on kennedy after failed monitor:
rc=7 (update=value++, time=1369304192)<br>
May 23 14:16:32 kennedy crmd[1787]: notice: do_state_transition:
State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC
cause=C_FSA_INTERNAL origin=abort_transition_graph ]<br>
May 23 14:16:32 kennedy attrd[20891]: notice:
attrd_trigger_update: Sending flush op to all hosts for:
fail-count-wcs_wcsd (1)<br>
May 23 14:16:32 kennedy pengine[1783]: notice: unpack_config: On
loss of CCM Quorum: Ignore<br>
May 23 14:16:32 kennedy pengine[1783]: warning: unpack_rsc_op:
Processing failed op monitor for wcs_wcsd on kennedy: not running
(7)<br>
May 23 14:16:32 kennedy attrd[20891]: notice:
attrd_perform_update: Sent update 230: fail-count-wcs_wcsd=1<br>
<br>
Is this a bug, or expected behaviour, or did I miss something from
documentation?<br>
<br>
Thanks in advance,<br>
Alexandr<br>
</body>
</html>