Comment 1 for bug 1247232
Revision history for this message
| Curtis Hovey (sinzui) wrote Re: Juju 1.16.0 deploys agent version 1.16.2 | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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.
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.