[ClusterLabs] Reason for changing a meta_attribute in the CIB

Detlef Gossrau detlef.gossrau at enghouse.com
Wed Jul 1 09:31:05 UTC 2015


Hi all,

how can I find the reason for changing a meta_attribute of a lsb 
resource in the CIB ? All what I see in /var/log/messages is

Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<configuration >
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: +     <resources >
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<primitive class="lsb" id="resRecorder" type="andphone" >
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<meta_attributes id="resRecorder-meta_attributes" >
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<nvpair id="resRecorder-meta_attributes-target-role" name="target-role" 
value="Stopped" __crm_diff_marker__="added:top" />
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
</meta_attributes>
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<meta_attributes id="resRecorder-meta_attributes-0" >
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
<nvpair id="resRecorder-meta_attributes-0-target-role" 
name="target-role" value="Stopped" __crm_diff_marker__="added:top" />
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
</meta_attributes>
Jun 25 11:51:10 muc-ant-02 crmd[1215]:     info: abort_transition_graph: 
te_update_diff:126 - Triggered transition abort (complete=1, tag=diff, 
id=(null), magic=NA, cib=0.118.1) : Non-status change
Jun 25 11:51:10 muc-ant-02 crmd[1215]:   notice: do_state_transition: 
State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC 
cause=C_FSA_INTERNAL origin=abort_transition_graph ]
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
</primitive>
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: +     </resources>
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + 
</configuration>
Jun 25 11:51:10 muc-ant-02 cib[1210]:     info: cib:diff: + </cib>

After that the ressource is stopped.

Is there a possibility to set a debug level to get more information ? I 
can't find any hint or dependency why the meta_attribute is changed.

Test environment on both nodes:

OS         : Linux 2.6.32-504.8.1.el6.x86_64
Cluster SW : pacemaker-cluster-libs-1.1.7-6.el6.x86_64
              pacemaker-libs-1.1.7-6.el6.x86_64
              pacemaker-cli-1.1.7-6.el6.x86_64
              pacemaker-1.1.7-6.el6.x86_64
              corosynclib-1.4.1-17.el6.x86_64
              corosync-1.4.1-17.el6.x86_64

Thnx for any help !

Best regards,
Detlef




More information about the Users mailing list