Comment 0 for bug 1247232

Revision history for this message
Aaron Bentley (abentley) wrote : Juju 1.16.0 deploys agent version 1.16.2

juju 1.16.0 deploys agent version 1.16.2. This means that the behaviour of juju can change when a new version of the agent is uploaded, even when the user has not upgraded their juju install. Juju should deploy the same-version agent, to avoid behaviour changes. If for some reason there's a desire to deploy mismatched client/agent combinations, an override can be provided.

Users can then upgrade their juju client and run upgrade-juju, which is the approach that CI testing tests. Upgrading the agent first is untested, so we cannot be confident that it will behave as desired.