Juju 1.22.6 cannot upgrade to 1.24.3/1.24.4

[Curtis Hovey]

Juju 1.22.x users cannot upgrade to 1.24.x as seen
    http://reports.vapour.ws/releases/2934/job/aws-upgrade-22-trusty-amd64/attempt/2
    http://reports.vapour.ws/releases/2934/job/hp-upgrade-22-trusty-amd64/attempt/3

This issue is true for 1.24.3 and 1.24.4

[Cheryl Jennings (cherylj)]

I was able to recreate on AWS going from 1.22.6 -> 1.24.3. The last thing I see in the log for machine 0 is:

machine-0: 2015-07-30 19:29:54 DEBUG juju.storage managedstorage.go:291 managed resource entry created with path "environs/f26976fd-d489-4bcd-821e-c6ed7ce9e76c/tools/1.24.3-trusty-amd64-4033bc556896cec7fd1bc977d95f18f4218676ce5a69d0e8b7afa3eb1389af6e" -> "6d22656b2476c40ab87d2b29b59d8bbf1bf1522e9fd4c9757eca86b221434a5d29913dd8b8070fb3822609e50e3b9e0a"

I'm going to add some more debugging hooks and try to recreate again.

Are the logs available for the test machines hitting this issue? I'd like to verify that this is the same problem.

[Canonical Juju QA Bot (juju-qa-bot)]

Juju-CI verified that this issue is Fix Released in juju-core 1.24:
    http://reports.vapour.ws/releases/2934

[Curtis Hovey (sinzui)]

^ The tests show otherwise they show upgrade from current stable pass
    http://reports.vapour.ws/releases/2934
but
    aws-upgrade-22-trusty-amd64
   hp-upgrade-22-trusty-amd64
did fail. They were temporarilly made non-voting, and CI saw its change to close this bug.

[Menno Finlay-Smits (menno.smits)]

The AWS and HP upgrade test which were failing earlier are now passing.

[Canonical Juju QA Bot (juju-qa-bot)]

Juju-CI verified that this issue is Fix Released in juju-core 1.24:
    http://reports.vapour.ws/releases/2937

[Curtis Hovey (sinzui)]

I marked this issue fix released i master after reviewing
    http://reports.vapour.ws/releases/2936

We are sure the failure was caused by another bug that a new test discovered. The jobs that first found this issue passes and it passes just as the confirmed 1.24 fix ran.