unit "started" status is unhelpful
Bug #1254766 reported by
William Reade
This bug affects 12 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Ian Booth | ||
Bug Description
The unit agent marks itself "started" as soon as the "start" hook has completed; but this isn't enough to determine the actual status of the unit. We should allow users to distinguish between a unit that's still "working" (joining relations, running hooks, upgrading charms, etc) or "ready" (idle -- waiting for further changes).
The precise mechanism isn't critically important -- although it's probably better to use the status-data field than the status-info field, because we expect people to parse it -- but it's important that this information be exposed in `juju status` as well as over the API's AllWatcher.
| Changed in juju-core: | |
| milestone: | none → 2.0 |
| tags: | added: hooks relations status |
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #1 |
| tags: | added: landscapee |
| tags: |
added: landscape removed: landscapee |
| tags: | added: usability |
| Changed in juju-core: | |
| importance: | High → Medium |
| tags: | added: cloud-installer |
| tags: | added: canonical-is canonical-webops papercut |
| tags: | added: ubuntu-engineering |
| tags: | added: cts |
| tags: | removed: cts |
Revision history for this message
| Ian Booth (wallyworld) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| milestone: | none → 1.24-beta1 |
| status: | Triaged → Fix Released |
To post a comment you must log in.
adding some search bait so this can be found.. units should show pending hook execution and steady state should be discoverable.