Incompatible version formats

[Jacek Nykis]

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-trusty-amd64"

To get it to work I had to remove "-trusty-amd64" from the version number.

Can juju version format be unified across all commands?

[Dimiter Naydenov (dimitern)]

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.

[Jacek Nykis (jacekn)]

Maybe upgrade-juju can be improved to print warning, ignore arch and series and carry on? From user's perspective it will "Just Work" and warning message will tell them what is the correct version format upgrade-juju expects.

If that is not possible maybe the error message can be improved to suggest version to use?

[Cheryl Jennings (cherylj)]

It would improve usability to have juju extract the version number from the string. Adding as a wish list item.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.