Incompatible version formats
Bug #1516975 reported by
Jacek Nykis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Wishlist
|
Unassigned |
Bug Description
After juju upgrade I wanted to upgrade my agents. I checked juju version like this:
$ juju --version
1.24.4-trusty-amd64
And tried using that as argument to "juju upgrade-juju" which failed:
$ juju upgrade-juju --version 1.24.4-trusty-amd64
error: invalid version "1.24.4-
To get it to work I had to remove "-trusty-amd64" from the version number.
Can juju version format be unified across all commands?
affects: | juju-core → juju |
To post a comment you must log in.
The version you pass to upgrade-juju is a version number, not a tools binary version (which includes the arch and series). It is documented as such in $ juju upgrade-juju --help.
Specifying arch and series is actually wrong, as the environment might have machines running other arch/series, but the same version number.