Upgrade fails on windows machines

[Martin Packman]

The new ci windows upgrade job fails as the upgrade never completes.

The setup is the same as all our other upgrade jobs, going from current stable (1.24) to tip of the branch tested (either 1.24~ or 1.25~). The job runs on maas 1.8 in kvms and uses a trusty state server and two win2012hvr2 machines with windows test charms deployed.

<http://reports.vapour.ws/releases/2851/job/maas-1_8-upgrade-win2012hvr2-amd64/attempt/10>

Log from the trusty state server (starts 14:42, upgrade happens 15:03, gives up 15:23):

<http://data.vapour.ws/juju-ci/products/version-2851/maas-1_8-upgrade-win2012hvr2-amd64/build-10/machine-0.log.gz>

Log from a machine with a windows unit (starts 15:02, sees upgrade 15:03 and dies shortly afterwards):

<http://data.vapour.ws/juju-ci/products/version-2851/maas-1_8-upgrade-win2012hvr2-amd64/build-10/machine-1.log.gz>

[Gabriel Samfira (gabriel-samfira)]

We actually already started working on this. Will update with progress later on.

[Martin Packman (gz)]

Fixes proposed for master:

<http://reviews.vapour.ws/r/2106/>
<http://reviews.vapour.ws/r/2109/>

[Menno Finlay-Smits (menno.smits)]

Removing blocker tag because the problem exists in 1.24.2 so the windows upgrade CI test upgrades from this version. That test will never pass until 1.24.3 (which needs to include the fix) is released.

Bogdan has made the changes to fix windows upgrades and has verified they fix the problem through manual upgrade checks. These have been merged into the master and 1.24 branches.

[Menno Finlay-Smits (menno.smits)]

Urgh. That first sentence should have been: Removing blocker tag because the problem exists in 1.24.2 and the windows upgrade CI test upgrades from this version.