Skipped TestUniterUpgradeConflicts on ppc64

Bug #1448308 reported by Martin Packman on 2015-04-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Low
Unassigned

Bug Description

TestUniterUpgradeConflicts has been consistently failing in the ppc64 across recent test runs.

<http://reports.vapour.ws/releases/2561/job/run-unit-tests-trusty-ppc64el/attempt/2847>

FAIL: uniter_test.go:874: com_juju_juju_worker_uniter_test.TestUniterUpgradeConflicts.pN51_github.com_juju_juju_worker_uniter_test.UniterSuite
...
[LOG] 0:02.965 INFO juju.worker.leadership u/0 got wait request for u leadership loss
[LOG] 0:02.965 INFO juju.worker.leadership u/0 still has u leadership
[LOG] 0:02.965 INFO juju.worker.leadership waiting for u/0 to lose u leadership
[LOG] 0:02.966 DEBUG juju.worker.uniter [AGENT-STATUS] idle
[LOG] 0:02.966 DEBUG juju.apiserver <- [C8] unit-u-0 {"RequestId":237,"Type":"Uniter","Version":2,"Request":"SetAgentStatus","Params":"'params redacted'"}
[LOG] 0:02.971 DEBUG juju.apiserver -> [C8] unit-u-0 4.765ms {"RequestId":237,"Response":"'body redacted'"} Uniter[""].SetAgentStatus
want resolved mode "", got "no-hooks"; still waiting
...
want resolved mode "", got "no-hooks"; still waiting
[LOG] 0:05.390 INFO juju.mongo dialled mongo successfully on address "[::1]:60357"
want resolved mode "", got "no-hooks"; still waiting
...
want resolved mode "", got "no-hooks"; still waiting
util_test.go:722:
    c.Fatalf("never reached desired status")
... Error: never reached desired status

[LOG] 0:12.970 INFO juju.worker.uniter ModeAbide exiting

The uniter tests have long been somewhat flakey in the ppc test run, but this one may well just be broken since the leadership landing.

Changed in juju-core:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers