Comment 8 for bug 1793514

I think the issue is that you have to upgrade the controller first, which
is currently "juju upgrade-juju -m controller", and *then* you can upgrade
individual model agents (juju upgrade-model).

On Thu, Sep 20, 2018 at 4:20 PM Jacek Nykis <email address hidden>
wrote:

> Public bug reported:
>
> juju status told me I had upgrade available:
>
> $ juju status
> Model Controller Cloud/Region Version SLA
> Timestamp Notes
> controller canonistack-lcy01 canonistack/lcy01 2.4.1 unsupported
> 13:01:52+01:00 upgrade available: 2.4.3
>
> So I tried to upgrade:
> $ juju upgrade-model
> no upgrades available
> $ juju upgrade-juju
> no upgrades available
>
> It's not clear whether the upgrade really is available or not. If it is
> then juju client should handle it better.
> I think first improvement could be to ensure that "juju status" and "juju
> upgrade-{juju,model}" use the same method to detect available upgrades.
>
> juju client I'm running is 2.4.1-xenial-amd64
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1793514
>
> Title:
> "upgrade available" in juju status is misleading
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1793514/+subscriptions
>