Comment 7 for bug 1570917

I realized there is a separate issue at play. Apparently the machine was provisioned at the (uploaded) version on the controller, rather than the model's.

This problem is exacerbated when the upgrader runs into the apparent downgrade to the model's version. The model did not have the original tools available, which it certainly should since it is that is the version it is running. However, this matter should be resolved by the previously referenced patch.

So at this point the reported trouble should no longer happen. I'm posting to juju-dev today about auto-upgrading models. I've opened lp:1573742 to address the matter of machines being initially provisioned to the admin model's version.

@Roger, please let us know if you're still having a problem with this.