Comment 2 for bug 1247232

On Sat, Nov 2, 2013 at 6:38 AM, Curtis Hovey <email address hidden> wrote:
> We have an upgrade-juju --version=XXX command that explicitly sets the
> version to be deployed, Users can use that now if they wish. The
> bootstrap command also has options to select tools from a series, but
> not version. I think then, that bootstrap should only choose the same
> version as the client. the user can upgrade if they wish, or upgrade-
> juju to just update the agents.

This is a regression. Tools selection should only allow an exact
match, ie, the client version and the initial agent version must
match.

>
> If there is a legitimate use case for selecting a different version, it
> needs to be better understood. I suspect this surprising bootstrap
> behaviour exists to ensure an agent can be deployed when there isn't a
> match. Choosing the newest tool does not meet this use case.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1247232
>
> Title:
> Juju 1.16.0 deploys agent version 1.16.2
>
> Status in juju-core:
> Triaged
>
> Bug description:
> 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 by Canonical, 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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1247232/+subscriptions