Comment 46 for bug 2056193

To complete John's remarks on the retrieved logs, here are other takeovers from today's debug session.

As Caner correctly pointed out, the django charm had the `peer` metadata set to false in one of the logs that we were verifying, and indeed the value should have been true as we verified on the charm itself. Now this might not have a direct impact in the bug we are seeing but it's something to follow up.

John also noted that we have a code path in the actionsResolver that will return an `ErrNoOperation` in some cases:

https://github.com/juju/juju/blob/3.1/worker/uniter/actions/resolver.go#L56-L71

We should better log, we have 3 possible return cases in that snippet.

We continued testing exec actions (`hostname`) into both units (`httprequest-lego-provider` and `nginx-ingress-integrator`) to double check that they got pending in httprequest-lego-provider until a timeout of 5 minutes.

On top of the db queries and logs that I posted in https://bugs.launchpad.net/juju/+bug/2056193/comments/44 we also retrieved a full log of the agent and controller for a detailed inspection.

The following steps are to analyze everything we were able to retrieve and therefore unblock Tom for further debug.