Comment 1 for bug 1993334

From the logs, looks like the charm is stuck in the config changed hook:

To start the hook executution:
2022-10-18 13:58:37 DEBUG juju.machinelock machinelock.go:176 machine lock "machine-lock" acquired for juju-lint/0 uniter (run config-changed hook)
2022-10-18 13:58:37 DEBUG juju.worker.uniter.operation executor.go:135 preparing operation "run config-changed hook" for juju-lint/0
219 2022-10-18 13:58:37 DEBUG juju.worker.uniter.operation executor.go:135 executing operation "run config-changed hook" for juju-lint/0

Usually when finished:
229 2022-10-18 13:58:37 DEBUG juju.worker.uniter.remotestate watcher.go:650 got config change for juju-lint/0: ok=true, hashes=[b9faa1f948a0e1b6cbb819711cc8f94a4c0fc21c0dd531b97 610cce62609fde9]
230 2022-10-18 13:58:37 INFO juju.worker.uniter.operation runhook.go:173 ran "config-changed" hook (via hook dispatching script: dispatch)
231 2022-10-18 13:58:37 DEBUG juju.worker.uniter.operation executor.go:135 committing operation "run config-changed hook" for juju-lint/0
232 2022-10-18 13:58:37 DEBUG juju.machinelock machinelock.go:206 created rotating log file "/var/log/juju/machine-lock.log" with max size 10 MB and max backups 5
233 2022-10-18 13:58:37 DEBUG juju.machinelock machinelock.go:190 machine lock "machine-lock" released for juju-lint/0 uniter (run config-changed hook)
234 2022-10-18 13:58:37 DEBUG juju.worker.uniter.operation executor.go:124 lock released for juju-lint/0

However the first last config changed hook, we never get the 2nd half. The machine lock is held.