On Fri, 2022-10-21 at 13:05 +0200, Lentes, Bernd wrote: > ----- On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@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 ?
It was by design, though that aspect of it was questionable. > And what is the conclusion of it all ? >From the rest of the thread, I suspect that this has been fixed in a later version, though I'm not sure which changes were relevant. A lot of work has been done on the digest code in the past couple years. > Do a "crm resource cleanup" before each "crm resource [un]trace" ? > And test everything with ptest before commit ? > > Bernd -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
