© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
So we sorted out the logic of how it could fail.
Unit agents in 1.18 now watch the version of their associated Machine agent. So DesiredVersion returns the version of the Machine agent in 1.18.
However, 1.16 agents just all watch the global environment configuration value.
Which means there is a race. If
1) Unit agent and API server both see the updated DesiredVersion and download and install their tools.
2) Machine agent has not seen it yet (or is still downloading)
3) API And Unit agent upgrade themselves and start running the new code.
At this point, the Unit Agent will check and see that it should be running the same version as its Machine, which is now older than its current version.
I'm not sure how to fix it, but at least we can understand *why* it is happening.