upgrade-controller happy to upgrade to a version that doesn't exist
Bug #1836260 reported by
Tim McNamara
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
upgrade-controller always seems to think that the agent binary is the build version of the requested --agent-version.
$ juju version
2.6.6-cosmic-amd64
$ juju upgrade-controller --agent-
best version:
2.9.0.1
started upgrade to 2.9.0.1
$ juju upgrade-controller --agent-
no prepackaged agent binaries available, using local agent binary 2.19.0.1
best version:
2.19.0.1
started upgrade to 2.19.0.1
$ juju upgrade-controller --agent-
no prepackaged agent binaries available, using local agent binary 55.9.43.1
best version:
55.9.43.1
started upgrade to 55.9.43.1
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | High → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.