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.
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.