juju status does not report the actual upgrade available for model

Bug #1832894 reported by Drew Freiberger on 2019-06-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

It is very misleading to run "juju status -m controller" and see:

Model Controller Cloud/Region Version SLA Timestamp Notes
controller ddmi-ok-nonprod foundations-maas 2.5.2 unsupported 19:13:08Z upgrade available: 2.5.7

and then to run:

juju upgrade-model -m controller

and have it pull down 2.6.3:

best version:
    2.6.3
started upgrade to 2.6.3

This upgrade available 2.5.7 note lulled me into thinking my client was 2.5.7 and that I could upgrade it to that level with a simple upgrade-model command without having to specify the agent version.

Obviously, I know this is a user error, however, the misleading juju status report could lead to disasterous results of upgrading past your approved and vetted juju series, for instance, if you were trying to track juju 2.5.x only.

So the controller polls periodically to find out whether there is an update
available. It is always possible that from the time we last saw there was
an upgrade until the time you issue "juju upgrade-controller" that there is
a new upgrade available. We reported what version we found when you issued
the upgrade. Is it that you would prefer a validation step "do you want to
upgrade to X.Y" if you didn't otherwise specify a version?
I don't think it makes sense to tie the upgrade to what might have been
seen on "juju status", and juju internally could just as easily have seen a
new version in its next "is there an update check" from the time you did
"juju status" until you did "juju upgrade-*".
Given that automatically selecting the newest version of Juju has been CLI
behavior, we'd probably have to add a flag "juju upgrade-controller
-verify-version" (or something shorter, but nothing immediately jumps out
at me.)

On Fri, Jun 14, 2019 at 11:25 PM Drew Freiberger <email address hidden>
wrote:

> Public bug reported:
>
> It is very misleading to run "juju status -m controller" and see:
>
> Model Controller Cloud/Region Version SLA
> Timestamp Notes
> controller ddmi-ok-nonprod foundations-maas 2.5.2 unsupported
> 19:13:08Z upgrade available: 2.5.7
>
>
> and then to run:
>
> juju upgrade-model -m controller
>
> and have it pull down 2.6.3:
>
> best version:
> 2.6.3
> started upgrade to 2.6.3
>
>
> This upgrade available 2.5.7 note lulled me into thinking my client was
> 2.5.7 and that I could upgrade it to that level with a simple upgrade-model
> command without having to specify the agent version.
>
> Obviously, I know this is a user error, however, the misleading juju
> status report could lead to disasterous results of upgrading past your
> approved and vetted juju series, for instance, if you were trying to
> track juju 2.5.x only.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
>
> ** Tags: canonical-bootstack
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1832894
>
> Title:
> juju status does not report the actual upgrade available for model
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1832894/+subscriptions
>

Changed in juju:
status: New → Triaged
status: Triaged → Incomplete
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
Changed in juju:
status: Expired → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers