On Thu, Oct 05, 2017 at 04:53:38AM -0000, Anastasia wrote:
> For historical reasons, your local client can only bootstrap controller with the same major.minor versions.
> In other words, 2.0 client can only bootstrap controllers using 2.0.x agents; 2.1 client can only bootstrap 2.1.x agents, etc.
>
> I have updated the error message at bootstrap to be more explicit:
> https://github.com/juju/juju/pull/7911.
>
> However, we have no intention of changing this behavior in the future.
> We want to avoid pitfalls where bootstrap may become incompatible
> between Juju versions.
I understand this reasoning, but we need a method to bootstrap old versions when using snaps, currently with deb packages I keep around in different PPAs each release (2.0, 2.1, etc). If juju could keep a track for each major.minor would be great.
The only method we will have is to compile locally the version needed.
On Thu, Oct 05, 2017 at 04:53:38AM -0000, Anastasia wrote: /github. com/juju/ juju/pull/ 7911.
> For historical reasons, your local client can only bootstrap controller with the same major.minor versions.
> In other words, 2.0 client can only bootstrap controllers using 2.0.x agents; 2.1 client can only bootstrap 2.1.x agents, etc.
>
> I have updated the error message at bootstrap to be more explicit:
> https:/
>
> However, we have no intention of changing this behavior in the future.
> We want to avoid pitfalls where bootstrap may become incompatible
> between Juju versions.
I understand this reasoning, but we need a method to bootstrap old versions when using snaps, currently with deb packages I keep around in different PPAs each release (2.0, 2.1, etc). If juju could keep a track for each major.minor would be great.
The only method we will have is to compile locally the version needed.