"upgrade available" in juju status is misleading
Bug #1793514 reported by
Jacek Nykis
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
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 client I'm running is 2.4.1-xenial-amd64
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju: | |
milestone: | 2.5-beta1 → 2.5-beta2 |
Changed in juju: | |
assignee: | Richard Harding (rharding) → Heather Lanigan (hmlanigan) |
status: | Triaged → In Progress |
Changed in juju: | |
assignee: | Heather Lanigan (hmlanigan) → nobody |
milestone: | 2.5-beta2 → none |
importance: | High → Medium |
Changed in juju: | |
status: | New → Triaged |
To post a comment you must log in.
Can you provide more details on the setup.
Is this a controller you owned and bootstrapped? Are you admin on it?
I believe the model should only show the upgrade available if the controller is up to that version and models on that controller are eligible to upgrade. I wonder if this is that you're not of high enough permissions to upgrade and that error isn't clear or if there's different logic in checking if an upgrade is available and we need to update that end.