Unit test failure: ClientPersistenceSuite.TestNewClientInvalidLeaseDoc

Bug #1618189 reported by Seman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned

Bug Description

As seen at
    http://reports.vapour.ws/releases/issue/57c49136749a565b5bf7b92c

Unit test failure in ClientPersistenceSuite.TestNewClientInvalidLeaseDoc as seen here:

http://reports.vapour.ws/releases/4319/job/run-unit-tests-xenial-ppc64el/attempt/762

----

FAIL: client_persistence_test.go:43: ClientPersistenceSuite.TestNewClientInvalidLeaseDoc

[LOG] 0:00.004 DEBUG juju.testing tls.Dial(127.0.0.1:38173) failed with local error: unexpected message
client_persistence_test.go:60:
    c.Check(err, gc.ErrorMatches, `corrupt lease document "snagglepuss": inconsistent _id`)
... error string = "Closed explicitly"
... regex string = "corrupt lease document \"snagglepuss\": inconsistent _id"

OOPS: 61 passed, 1 FAILED
--- FAIL: TestPackage (3.84s)

Tags: ci regression
Changed in juju:
milestone: none → 2.1.0
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue has not been seen for 6 months.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.