I'm still having to deal with this issue frequently. If I run debug-hooks, I will end up in a not-properly-initialised tmux environment:
--------------------------------------------------
root@controller-0:/var/lib/juju#
--------------------------------------------------
I'm not in the right directory, and more importantly, the environment is not properly set up, so I can't run any of the hooks. I get issues like "JUJU_UNIT_NAME not set" and so forth.
Sometimes I have to wait several minutes for the environment to jump to the "correct" screen (i.e. where it should have taken me initially:
--------------------------------------------------
This is a Juju debug-hooks tmux session. Remember:
1. ...
--------------------------------------------------
This is really impacting the usefulness of this debug-hooks tool for charm developers.
I'm still having to deal with this issue frequently. If I run debug-hooks, I will end up in a not-properly- initialised tmux environment: ------- ------- ------- ------- ------- ------- - -0:/var/ lib/juju# ------- ------- ------- ------- ------- ------- -
-------
root@controller
-------
I'm not in the right directory, and more importantly, the environment is not properly set up, so I can't run any of the hooks. I get issues like "JUJU_UNIT_NAME not set" and so forth.
Sometimes I have to wait several minutes for the environment to jump to the "correct" screen (i.e. where it should have taken me initially: ------- ------- ------- ------- ------- ------- - ------- ------- ------- ------- ------- ------- -
-------
This is a Juju debug-hooks tmux session. Remember:
1. ...
-------
This is really impacting the usefulness of this debug-hooks tool for charm developers.