UniterSuite.TestUniterUpgradeConflicts fails

[Aaron Bentley]

As seen here:
http://reports.vapour.ws/releases/issue/554cd810749a564a9453e742

I assume this is intermittent, because the code successfully landed.

The symptoms don't resemble bug #1311825 so I do not consider it a dupe.

Snippet:
FAIL: uniter_test.go:856: UniterSuite.TestUniterUpgradeConflicts

[LOG] 0:00.014 DEBUG juju.environs.configstore Made dir /tmp/check-3400114664489187467/525/home/ubuntu/.juju/environments
[LOG] 0:00.124 DEBUG juju.environs.configstore writing jenv file
[LOG] 0:00.125 DEBUG juju.environs.configstore writing jenv file to /tmp/check-3400114664489187467/525/home/ubuntu/.juju/environments/dummyenv.jenv
[LOG] 0:00.125 DEBUG juju.environs.tools reading v1.* tools
[LOG] 0:00.125 INFO juju.environs.testing uploading FAKE tools 1.24-alpha1-trusty-amd64
[LOG] 0:00.127 INFO juju.environs.testing uploading FAKE tools 1.24-alpha1-precise-amd64
[LOG] 0:00.140 INFO juju.environs.testing uploading FAKE tools 1.24-alpha1-utopic-amd64
[LOG] 0:00.142 INFO juju.environs.tools Writing tools/streams/v1/index2.json
[LOG] 0:00.142 INFO juju.environs.tools Writing tools/streams/v1/index.json
[LOG] 0:00.143 INFO juju.environs.tools Writing tools/streams/v1/com.ubuntu.juju-released-tools.json
[LOG] 0:00.143 DEBUG juju.environs.simplestreams read metadata index at "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json"
[LOG] 0:00.144 DEBUG juju.environs.simplestreams metadata: &{map[com.ubuntu.juju:12.04:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc210dcd060]} com.ubuntu.juju:14.04:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc210dcd180]} com.ubuntu.juju:14.10:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc210dcd2a0]}] map[] Thu, 09 Apr 2015 00:22:46 +0000 products:1.0 com.ubuntu.juju:released:tools }
[LOG] 0:00.144 DEBUG juju.environs.simplestreams read metadata index at "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json"
[LOG] 0:00.144 DEBUG juju.environs.simplestreams skipping index "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json" because of missing information: "content-download" data not found
[LOG] 0:00.144 DEBUG juju.environs.simplestreams read metadata index at "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json"
[LOG] 0:00.145 DEBUG juju.environs.simplestreams skipping index "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json" because of missing information: "content-download" data not found
[LOG] 0:00.145 DEBUG juju.environs.simplestreams read metadata index at "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json"
[LOG] 0:00.145 DEBUG juju.environs.simplestreams skipping index "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json" because of missing information: "content-download" data not found
[LOG] 0:00.146 INFO juju.environs.tools Metadata for stream "released" unchanged
[LOG] 0:00.146 INFO juju.environs.tools Writing tools/streams/v1/index2.json
[LOG] 0:00.146 INFO juju.environs.tools Writing tools/streams/v1/index.json
[LOG] 0:00.146 INFO juju.network setting prefer-ipv6 to true
[LOG] 0:00.146 DEBUG juju.environs.bootstrap environment "dummyenv" supports service/machine networks: true
[LOG] 0:00.146 DEBUG juju.environs.bootstrap network management by juju enabled: true
[LOG] 0:00.146 DEBUG juju.environs.bootstrap looking for bootstrap tools: version=1.24-alpha1
[LOG] 0:00.146 INFO juju.environs.tools reading tools with major.minor version 1.24
[LOG] 0:00.146 INFO juju.environs.tools filtering tools by version: 1.24-alpha1
[LOG] 0:00.147 DEBUG juju.environs.simplestreams read metadata index at "file:///tmp/check-3400114664489187467/528/tools/streams/v1/index2.json"
[LOG] 0:00.148 DEBUG juju.environs.simplestreams metadata: &{map[com.ubuntu.juju:12.04:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc2106f0d20]} com.ubuntu.juju:14.04:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc2106f0e40]} com.ubuntu.juju:14.10:amd64:{ 1.24-alpha1 amd64 map[20150409:0xc2106f0f60]}] map[] Thu, 09 Apr 2015 00:22:46 +0000 products:1.0 com.ubuntu.juju:released:tools }
[LOG] 0:00.193 INFO juju.network setting prefer-ipv6 to true
[LOG] 0:00.193 INFO juju.provider.dummy would pick tools from 1.24-alpha1-trusty-amd64
[LOG] 0:00.193 INFO juju.provider.dummy creating bootstrap instance
[LOG] 0:00.193 INFO juju.state opening state, mongo addresses: ["[::1]:44948" "localhost:44948"]; entity <nil>
[LOG] 0:00.193 DEBUG juju.state dialing mongo
[LOG] 0:00.200 INFO juju.mongo dialled mongo successfully on address "[::1]:44948"
[LOG] 0:00.201 DEBUG juju.state connection established
[LOG] 0:00.210 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:44948"
[LOG] 0:00.301 INFO juju.state initializing environment, owner: "dummy-admin@local"

...

[LOG] 0:14.736 DEBUG juju.apiserver -> [BC] user-dummy-admin@local 11.777376ms {"RequestId":1,"Response":"'body redacted'"} Admin[""].Login
[LOG] 0:14.743 DEBUG juju.state setting API hostPorts: [[localhost:33489]]
[LOG] 0:14.745 DEBUG juju.environs.configstore writing jenv file
[LOG] 0:14.746 DEBUG juju.environs.configstore writing jenv file to /tmp/check-3400114664489187467/531/home/ubuntu/.juju/environments/dummyenv.jenv
jenv host ports: [][]network.HostPort{[]network.HostPort{localhost:33489}}
[LOG] 0:14.753 INFO juju.provider.dummy reset environment
[LOG] 0:14.754 INFO juju.apiserver [BC] user-dummy-admin@local API connection terminated after 29.976514ms
[LOG] 0:14.760 INFO juju.testing reset successfully reset admin password
[LOG] 0:14.777 INFO juju.testing reset successfully reset admin password
[LOG] 0:14.780 INFO juju.testing reset successfully reset admin password
2015-04-09 00:23:41 WARNING juju.worker.uniter upgrade123.go:26 no uniter state file found for unit unit-mysql-0, skipping uniter upgrade step
OOPS: 43 passed, 1 FAILED
--- FAIL: TestPackage (492.47 seconds)
FAIL

[Martin Packman (gz)]

See also bug 1437445 which is another way for this test to fail.

[Curtis Hovey (sinzui)]

As seen in
    http://reports.vapour.ws/releases/issue/554cd810749a564a9453e742
this test is most likely to fail on golang 1.3+ or on under powered machines like i386 machines.

[Dimiter Naydenov (dimitern)]

Since this seems like a timeout issue, and there's an upcoming uniter sprint which will focus on such things, I'm about to propose a PR to skip this test only on i386.

[Dimiter Naydenov (dimitern)]

PR: https://github.com/juju/juju/pull/2907

Not closing this as it's not fixed and we'll need to take care of it, but with lower priority I guess.

[Alexis Bruemmer (alexis-bruemmer)]

Does this test still fail on the 1.26 branch?

[Alexis Bruemmer (alexis-bruemmer)]

Based on this log they are passing: http://reports.vapour.ws/releases/3100

But are we still seeing intermittent failures on 1.26?

[Aaron Bentley (abentley)]

We are seeing it on 1.25 and 1.24, but haven't seen it on master (1.26) since Sept 7.

Based on the issue: http://reports.vapour.ws/releases/issue/554cd810749a564a9453e742

[Curtis Hovey (sinzui)]

This issue might be fixed as we have not seen it in 9 days:
    http://reports.vapour.ws/releases/issue/554cd810749a564a9453e742