_is_ that the resource name though?
From one of your earlier examples:
It's an example from me not from Kiran.
# pcs resource clone groupPing clone-max=3 clone-node-max=1
# pcs resource
Clone Set: groupPing-clone [groupPing]
The name you should be passing to pcs is groupPing-clone, _not_ groupPing.
Please ignore me if you are already doing this. In that case its a bug for
Chris.
Chris: let me know if we're not exposing something you need.
Yes, I did. See below.
Maybe we should fork this to another thread since Kiran has trouble with
stopping multi-state resources and not with clones.
I had a similar problem with a cloned group and solved it by un-cloning
before deleting the group.
Maybe un-cloning the multi-state resource could help too.
It's easy to reproduce.
# pcs resource create resPing ping host_list="10.0.0.1 10.0.0.2" op monitor
on-fail="restart"
# pcs resource group add groupPing resPing
# pcs resource clone groupPing clone-max=3 clone-node-max=1
# pcs resource
Clone Set: groupPing-clone [groupPing]
Started: [ node1 node2 node3 ]
# pcs resource delete groupPing-clone
Deleting Resource (and group) - resPing
Error: Unable to remove resource 'resPing' (do constraints exist?)
# pcs resource unclone groupPing
# pcs resource delete groupPing
Removing group: groupPing (and all resources within group)
Stopping all resources in group: groupPing...
Deleting Resource (and group) - resPing
Log:
Feb 26 15:43:16 node1 cibadmin[2368]: notice: crm_log_args: Invoked:
/usr/sbin/cibadmin -o resources -D --xml-text <group id="groupPing">#012
<primitive class="ocf" id="resPing" provider="pacemaker" type="ping">#012
<instance_attributes id="resPing-instance_attributes">#012 <nvpair
id="resPing-instance_attributes-host_list" name="host_list" value="10.0.0.1
10.0.0.2"/>#012 </instance_attributes>#012 <operations>#012 <op
id="resPing-monitor-on-fail-restart" interval="60s" name="monitor"
on-fail="restart"/>#012 </operations>#012 </primi
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Expecting an element
meta_attributes, got nothing
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Invalid sequence in
interleave
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Element clone failed to
validate content
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Element resources has
extra
content: primitive
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Invalid sequence in
interleave
Feb 26 15:43:16 node1 cib[1820]: error: xml_log: Element cib failed to
validate content
Feb 26 15:43:16 node1 cib[1820]: warning: cib_perform_op: Updated CIB does
not validate against pacemaker-1.2 schema/dtd
Feb 26 15:43:16 node1 cib[1820]: warning: cib_diff_notify: Update (client:
cibadmin, call:2): 0.516.7 -> 0.517.1 (Update does not conform to the
configured schema)
Feb 26 15:43:16 node1 stonith-ng[1821]: warning: update_cib_cache_cb:
[cib_diff_notify] ABORTED: Update does not conform to the configured schema
(-203)
Feb 26 15:43:16 node1 cib[1820]: warning: cib_process_request: Completed
cib_delete operation for section resources: Update does not conform to the
configured schema (rc=-203, origin=local/cibadmin/2, version=0.516.7)
Frank
_______________________________________________
Pacemaker mailing list: Pacemaker@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
