Comment 5 for bug 1247232
Revision history for this message
| Aaron Bentley (abentley) wrote Re: Juju 1.16.0 deploys agent version 1.16.2 | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Regardless of what was intended behaviour, I think it is a bug because
- it prevents users from being able to deploy a specific version, which I understand some commercial users want to do.
- it exposes users to untested client/server combinations (whereas we do test the opposite combination, for upgrade purposes)
- it reduces the certainty that what worked today will work tomorrow
- it removes a safety valve: we believed that if a newly-published agent was buggy, we could avoid problems by simply withholding the corresponding client. But that is not true because a down-level client will deploy the buggy agent.
It is also a more complex rule than simply "the client bootstraps the agent that matches its version number".
Does it also mean that instances deployed after a new agent version becomes available will have different agent versions from one another, and so tend to cause environments to be a mix of different agents?