Comment 15 for bug 1893993

even with DEBUG logging I'm still not seeing stack traces, only:

2020-09-08 14:55:42 DEBUG juju.worker.logger logger.go:64 initial log config: "<root>=DEBUG"
2020-09-08 14:55:42 DEBUG juju.worker.logger logger.go:92 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING"
2020-09-08 15:03:14 ERROR juju.worker.uniter.operation runhook.go:136 hook "peer-relation-joined" (via explicit, bespoke hook script) failed: exit status 1

Curiously something is overriding the logging back to WARNING during runtime. That was a new model I deployed while already having the model-config set to <root>=DEBUG. Checking the model-config again, I see the model-config changed itself back to <root>=WARNING. That is not what I want and certainly not expected to happen, logging level shouldn't simply change itself automatically.