Service units get stuck in debug mode.

debug-hooks mode will exit when two things happen, there is no currently executing hook in the tmux window, and the admin client connection to zookeeper is closed. If the user closes the connection without exiting from the tmux session and a hook is currently executing, then the debug-hooks session is still active and the unit will wait on the hook to finish. Ideally we'd detect the end of the debug-session and forcibly terminate the debug-hook.

in the context of the pastebin example, its not really an example of the wedged unit, just that the debug-hook flag isn't cleared out eagerly but relies on zk ephemeral node deletion, which should be tied to the end of the session and client closing, so this behavior is a little odd.

Excerpts from Kapil Thangavelu's message of Fri Jan 27 02:24:34 UTC 2012:
> debug-hooks mode will exit when two things happen, there is no currently
> executing hook in the tmux window, and the admin client connection to
> zookeeper is closed. If the user closes the connection without exiting
> from the tmux session and a hook is currently executing, then the debug-
> hooks session is still active and the unit will wait on the hook to
> finish. Ideally we'd detect the end of the debug-session and forcibly
> terminate the debug-hook.
>
> ** Changed in: juju
> Status: New => Confirmed
>
> ** Changed in: juju
> Importance: Undecided => Low
>

Could we consider raising the importance a bit? debug-hooks is pretty
important, and if it is unreliable, that will be really frustrating
for users.