application version only exposed on application, not units
Bug #1641876 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apt layer |
Incomplete
|
Undecided
|
Unassigned | ||
| Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
| Snap Layer |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
The application version number is metadata on the application, rather than on the actual units. This means is is volatile and unhelpful when it is needed most, when doing software upgrades, or auditing/alerting to discover outdated software.
If the version running on the actual unit could be exposed in the yaml status output, that would be great. I understand there is no room for it on the standard tabular output (even though it would be cool to watch rolling upgrades of clusters happen in real time).
| tags: | added: canonical-is |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in layer-apt: | |
| status: | New → Incomplete |
| Changed in layer-snap: | |
| status: | New → Incomplete |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Adding layer-snap and layer-apt, as I was planning on having their update-status hooks check installed package version and update the juju version. However, units only know the version on that particular unit and determining a version for the whole application will require a peer relation.