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

Bug #1227942 reported by Kapil Thangavelu on 2013-09-20
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

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

John A Meinel (jameinel) on 2013-09-22
Changed in juju-core:
importance: Undecided → Medium
status: New → Triaged
tags: added: easy ui
Curtis Hovey (sinzui) on 2013-10-11
tags: added: hours
removed: easy
Changed in juju-core:
importance: Medium → Low
Curtis Hovey (sinzui) on 2013-10-15
tags: added: debug-hooks
Adam Israel (aisrael) wrote :

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.

Ian Booth (wallyworld) on 2015-07-21
Changed in juju-core:
importance: Low → High
milestone: none → 1.25.0
Curtis Hovey (sinzui) on 2015-08-13
Changed in juju-core:
milestone: 1.25.0 → 1.25.1
Changed in juju-core:
milestone: 1.25.1 → 1.26.0
Changed in juju-core:
milestone: 1.26.0 → 2.0-alpha2
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.0
Changed in juju-core:
milestone: 2.0.0 → 2.1.0
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
Curtis Hovey (sinzui) on 2016-08-22
Changed in juju:
milestone: none → 2.1.0
Anastasia (anastasia-macmood) wrote :

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

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

tags: added: usability
Changed in juju:
importance: High → Medium
milestone: 2.1.0 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers