Comment 17 for bug 1507867

RE: the issue with invalid binary version numbers when juju upgrade-juju is run

The flow is that the juju command asks the agent for all known tools so it can pick the ones to upgrade to. The agent will return all tools cached in state as well as one from simplestreams. For some reason, the tools in state were cached with an empty series in the metadata. When there records were shipped back to the upgrade command, it complained.

Clearing the cached tools metadata in state resolved the invalid binary version issue. The upgrade command gets further along, printing what tools it will use. The next step is for it to write the new agent-version setting to state to trigger the upgrade. But before it does this the client exists with a connection closed error. This is the next issue to diagnose.