On 3/22/12 5:09 AM, Ante Karamatic wrote:
Hi
I've came across an odd behavior, which might be considered as
inconsistent. As we know, pacemaker doesn't allow deleting a resource
that's running, but this doesn't produce same behavior every time.
Let's take a VM with a default stop timeout (90 seconds).
First behavior
--------------
# crm resource stop vm ; crm primitive delete vm
This will result with:
ERROR: resource vm is running, can't delete it
Eventually, vm resource will stop and delete can be 'reexecuted'. It
will be removed and everybody's happy. Ideally, IMHO, delete would be
queued.
When you stop the resource do 'crm -w resource stop vm'. it will wait
until the resource is stopped, rather than waiting for crm to run the
command.
David
_______________________________________________
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
