[ClusterLabs] crm resource trace (Was: Re: trace of resource - sometimes restart, sometimes not)

[Lentes, Bernd]

----- On 7 Oct, 2022, at 21:37, Reid Wahl nwahl at redhat.com wrote:

> On Fri, Oct 7, 2022 at 6:02 AM Lentes, Bernd
> <bernd.lentes at helmholtz-muenchen.de> wrote:
>> ----- On 7 Oct, 2022, at 01:18, Reid Wahl nwahl at redhat.com wrote:
>>
>> > How did you set a trace just for monitor?
>>
>> crm resource trace dlm monitor.
> 
> crm resource trace <rsc> <op> adds "trace_ra=1" to the end of the
> monitor operation:
> https://github.com/ClusterLabs/crmsh/blob/8cf6a9d13af6496fdd384c18c54680ceb354b72d/crmsh/ui_resource.py#L638-L646
> 
> That's a schema violation and pcs doesn't even allow it. I installed
> `crmsh` and tried to reproduce... `trace_ra=1` shows up in the
> configuration for the monitor operation but it gets ignored. I don't
> get *any* trace logs. That makes sense -- ocf-shellfuncs.in enables
> tracing only if OCF_RESKEY_trace_ra is true. Pacemaker doesn't add
> operation attribute to the OCF_RESKEY_* environment variables... at
> least in the current upstream main.
> 
> Apparently (since you got logs) this works in some way, or worked at
> some point in the past. Out of curiosity, what version are you on?
> 

SLES 12 SP5:
ha-idg-1:/usr/lib/ocf/resource.d/heartbeat # rpm -qa|grep -iE 'pacemaker|corosync'

libpacemaker3-1.1.24+20210811.f5abda0ee-3.21.9.x86_64
corosync-2.3.6-9.22.1.x86_64
pacemaker-debugsource-1.1.23+20200622.28dd98fad-3.9.2.20591.0.PTF.1177212.x86_64
libcorosync4-2.3.6-9.22.1.x86_64
pacemaker-cli-1.1.24+20210811.f5abda0ee-3.21.9.x86_64
pacemaker-cts-1.1.24+20210811.f5abda0ee-3.21.9.x86_64
pacemaker-1.1.24+20210811.f5abda0ee-3.21.9.x86_64


Bernd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2217 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20221010/bc9f08d7/attachment.p7s>