I notice that the local log file had these lines following the Juju uniter preamble:
2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 Operator Framework 1.5.4 up and running. 2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 Emitting Juju event reconcile_runners. 2023-02-14 14:46:40 DEBUG unit.runner/11.juju-log server.go:319 http://localhost:None "GET /1.0 HTTP/1.1" 200 None
Is it possible that the charm logic is using the juju exec/run trick to dispatch a custom hook, and that a misapplication of said trick is wedging the charm?
I notice that the local log file had these lines following the Juju uniter preamble:
2023-02-14 14:46:40 DEBUG unit.runner/ 11.juju- log server.go:319 Operator Framework 1.5.4 up and running. 11.juju- log server.go:319 Emitting Juju event reconcile_runners. 11.juju- log server.go:319 http:// localhost:None "GET /1.0 HTTP/1.1" 200 None
2023-02-14 14:46:40 DEBUG unit.runner/
2023-02-14 14:46:40 DEBUG unit.runner/
Is it possible that the charm logic is using the juju exec/run trick to dispatch a custom hook, and that a misapplication of said trick is wedging the charm?