What happened to pinned bootstrap

[John Meinel]

I thought at one point we were explicitly requiring that we bootstrap exact
versions of tools (so juju CLI 1.17.2 would only bootstrap a 1.17.2 set of
tools). We at least did 1.17 will only bootstrap 1.17, but looking at the
code we still always deploy the latest 1.17 (which broke all the 1.17
series of CLI because 1.17.7 has an incompatible required flag).

There is an argument that we can't get away with such a thing in a stable
series anyway, so it isn't going to be a problem. Mostly, though, I had
thought that we did exact matching, but I can see from the code that is
clearly not true.

Would it be very hard to do so? I think William had a very interesting idea
that CLI bootstrap would always only bootstrap the exact version of tools,
but could set the AgentVersion to the latest stable minor version, so it
essentially bootstraps and then immediately upgrades. (With the big benefit
that the upgrade process to migrate from old versions to new versions gets
run.)

This could be a distraction from the other stuff we're working on, but it
doesn't look that hard to implement, and would avoid some of these
semi-accidental breaking of old tools.

John
=:->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140330/79d3326f/attachment.html>