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.
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-c6ed7ce9e7 6c/tools/ 1.24.3- trusty- amd64-4033bc556 896cec7fd1bc977 d95f18f4218676c e5a69d0e8b7afa3 eb1389af6e" -> "6d22656b2476c4 0ab87d2b29b59d8 bbf1bf1522e9fd4 c9757eca86b2214 34a5d29913dd8b8 070fb3822609e50 e3b9e0a"
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.