[ClusterLabs] crm resource trace

[Lentes, Bernd]

----- On 17 Oct, 2022, at 21:41, Ken Gaillot kgaillot at redhat.com wrote:

> This turned out to be interesting.
> 
> In the first case, the resource history contains a start action and a
> recurring monitor. The parameters to both change, so the resource
> requires a restart.
> 
> In the second case, the resource's history was apparently cleaned at
> some point, so the cluster re-probed it and found it running. That
> means its history contained only the probe and the recurring monitor.
> Neither probe nor recurring monitor changes require a restart, so
> nothing is done.
> 
> It would probably make sense to distinguish between probes that found
> the resource running and probes that found it not running. Parameter
> changes in the former should probably be treated like start.
> 

Is that now a bug or by design ?
And what is the conclusion of it all ?
Do a "crm resource cleanup" before each "crm resource [un]trace" ?
And test everything with ptest before commit ?

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/20221021/827304d7/attachment.p7s>