Comment 31 for bug 2056193

I realise after looking into the latest info that the block action processing is not relevant for sidebar charms. It was intended for the case where an old style charm acted as an operator and created the workload in a separate pod.

I added some extra local debugging and can see that "ActionsBlocked" for sidevar charm should always be false; it should be that notification of pending actions is always acted on, and yet the logs show an action notification that is ignored.

Given hooks appear to be running, there's nothing obvious to explain why actions are being ignored.
There's also not enough logging in the right places to shed more light on it. And I can't reproduce locally with the snappass-test charm. I tried emulating what happened by first forcing a hook to fail and then refreshing the charm. Even with the failed hook, an action could still be run as is expected.

To make this easier to debug, more logging is needed but it doesn't help right now with the immediate problem.