juju debug-hooks unit/x should wait till unit is up

[Kapil Thangavelu]

juju debug-hooks should wait for a unit to be up rather than forcing a user to keep retrying or waiting (this per pyjuju behavior and good ux). ideally this should also allow for consistently being able to run debug-hooks on install and start hooks.

$ juju debug-hooks mysql/0
error: unit "mysql/0" has no public address

[Adam Israel (aisrael)]

To add another point of view to this bug:

I'm attempting to use the wip storage bits, and wanted to catch *-storage-attach, but the window between allocation and that hook being called can be very small. A very hacky workaround is to wrap the command in a tight loop, i.e.,

until juju debug-hooks my-unit/0 data-storage-attach; do
  echo "Waiting for unit to come online..."
done

and then call deploy.

With more storage functionality landing in 1.25, it seems like this might be a good time to re-evaluate the priority of this bug.

[Anastasia (anastasia-macmood)]

This behavior still exists. The error message on 2.1.x differs

$ juju debug-hooks <any charm>/0
ERROR no available address(es)

[Dmitrii Shcherbakov (dmitriis)]

Still the same as in #2.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.