juju show-model does not output the agent version for the model

Bug #1693530 reported by Richard Harding
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Anastasia

Bug Description

My understanding is that you not only need to upgrade the controller model but each other model in order to complete an upgrade:

https://jujucharms.com/docs/stable/models-upgrade#the-upgrade-juju-command

However, juju show-model does not output any information on the version. juju status does include the version information for the model and needs to be used instead, however it's much busier and not easily grep'able to tell if any models in your controller need to be upgraded.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Anastasia (anastasia-macmood)
milestone: none → 2.2-rc1
Changed in juju:
status: Triaged → In Progress
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am working on this right now, Rick. Am I correct in assuming that you'd like to see agent-version in yaml and json? I am trying to determine if I can leave tabular output as is...

Revision history for this message
Anastasia (anastasia-macmood) wrote :

To clarify, the underlying functionality - getting model details as well as presentation logic - is shared with "juju models" command. And I am wondering if I should also be displaying agent version as a result of "juju models" in tabular format :D

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1693530] Re: juju show-model does not output the agent version for the model

$ juju models
Controller: lxd

Model Cloud/Region Status Machines Cores Access Last
connection
controller lxd available 1 - admin just now
default* lxd available 0 - admin 58 seconds ago

Doesn't have a lot of text on it, and you could give a version in the
tabular format.
We've generally taken the stance that if you want to interact via script,
that is what JSON/YAML is for, so you shouldn't be scraping the tabular
form. So we're allowed to add things, etc.

My gut says that it probably isn't something people want to see all the
time, it is only valid at particular periods where there are new versions
that you want to roll out. Having it in --format=yaml seems sufficient for
that case.

Feedback from Rick is probably more useful on finding that line here.

On Mon, May 29, 2017 at 4:13 PM, Anastasia <email address hidden>
wrote:

> To clarify, the underlying functionality - getting model details as well
> as presentation logic - is shared with "juju models" command. And I am
> wondering if I should also be displaying agent version as a result of
> "juju models" in tabular format :D
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1693530
>
> Title:
> juju show-model does not output the agent version for the model
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1693530/+subscriptions
>

Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR against develop (2.2): https://github.com/juju/juju/pull/7413

Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
Richard Harding (rharding) wrote :

My feedback is that while the juju list-controllers and juju status always show the model version, that juju list-models is ok to not include it as long as it's in the machine readable format.

So +1 to not outputting in the table output, but including in JSON/YAML/etc.

Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.