Comment 1 for bug 1917333

It's hard to say exactly where the test failed since there's no stacktrace. But I don't think it's stuck waiting for a config-changed hook.

02:39:06 test_audit_custom_policy started
02:39:54 kubernetes-master/1 completes config-changed hook
02:42:08 kubernetes-master/1 acquires machine lock for juju-run (action 208), never releases it
03:09:06 test times out

Seems like it got stuck later in the test, maybe with one of the calls to juju run kubectl.

I'm marking this as incomplete since there's not much we can do with this report. Please fix:
https://github.com/juju/juju-crashdump/issues/81
https://github.com/juju/juju-crashdump/issues/82

so we can get some visibility into what these blocking juju-run calls are.