OK so this is different to the original bug in the hacluster relations for reactive charms, where services got restarted every 5 minutes (on update-status calls).
In this case the log data are someone random in timing but > 15-20 mins.
OK so this is different to the original bug in the hacluster relations for reactive charms, where services got restarted every 5 minutes (on update-status calls).
In this case the log data are someone random in timing but > 15-20 mins.