16.02.2015 11:15, Kristoffer Grönlund wrote:
Vladislav Bogdanov <bub...@hoster-ok.com> writes:
Hi Kristoffer,
may be it is worth to silently (or at least with rc=0) allow deletion of
non-existing or already-deleted configuration statements?
Background for that is that I keep track of the all configuration
statements myself, and, when I delete some resources (together with
accompanying constraints), they may go "out-of-order" to 'crm configure
delete', thus some constraints are automatically deleted when deleting
"lower" resource before the "upper" one. That leads to the whole crm
script to fail.
Hmm, I am not sure about doing this by default, since we would want to
show some kind of indication that a resource name may have been
misspelled for example... But I can imagine having a command line flag
for being more flexible in this regard.
Reuse '-F'?
I will look at how it works now.
BTW, I suspect that passing the --wait flag to crm while running
commands in this way may help you. Although I am not sure I entirely
understand what it is you are doing :)
Look:
crm configure
primitive a ...
primitive b ...
colocation b-with-a inf: b a
commit
exit
crm configure
delete a
delete b-with-a <= fails because is already deleted automatically
delete b
commit
Best,
Vladislav
Cheers,
Kristoffer
Best,
Vladislav
13.02.2015 17:03, Vladislav Bogdanov wrote:
Hi,
Following fails with the current crmsh (e4b10ee).
# crm resource stop cl-http-lv
# crm resource stop cl-http-lv
ERROR: crm_diff apparently failed to produce the diff (rc=0)
ERROR: Failed to commit updates to cl-http-lv
# echo $?
1
Best,
Vladislav
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
