>>> Dejan Muhamedagic <deja...@fastmail.fm> schrieb am 18.02.2015 um 11:04 in Nachricht <20150218100410.GA30682@tuttle.linbit>: > Hi, > > On Wed, Feb 18, 2015 at 08:21:10AM +0100, Ulrich Windl wrote: >> >>> Kristoffer Grönlund<kgronl...@suse.com> schrieb am 16.02.2015 um 09:15 in >> Nachricht <87oaougtlw....@krigpad.kri.gs>: >> > 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. >> >> I'd agree: Stopping a stopped resource is different from deleting a resource >> that does not exist (maybe never existed). Maybe (for scripting) crm shell >> would benefit from a "crm resource exists <rsc_name>" returning a status >> (yes/no/error). > > You could use crm resource status for that. It should exit with > error only if the resource doesn't exist. Ah! I haven't ried, but from what I thought "crm resource status" would output all resources, and I thought one had to parse the output for a single resource. Your answer suggests I can add a resource name to get just the resource I'm interested in. (Dind't know that) Trying that I found a minor problem for a clone resource with on node bing standby: -- crm(live)resource# status cln_cLVMd resource cln_cLVMd is running on: h01 resource cln_cLVMd is running on: h05 resource cln_cLVMd is NOT running -- Here it's not obvious on which node the resource is not running (missing " on: h??"). Regards, Ulrich > > Thanks, > > Dejan > > _______________________________________________ > 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
