"cannot create leadership lease client: corrupt lease document" on upgrade to 2.3-beta2

Bug #1728972 reported by Andrew Wilkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Andrew Wilkins

Bug Description

I've just upgraded from an earlier version of the develop branch to the most recent, and I see this error message spewed out a bunch of times:

ERROR juju.worker exited "leadership": cannot create leadership lease client: corrupt lease document "c6e63be8-b613-4d9f-8aa5-dd969d9fe13b:clock#application-leadership#": inconsistent _id

The error message eventually goes away.

What is happening is that we start the lease manager when opening a State object; that lease manager worker immediately fails with the above error. We then run the upgrade step that converts the old lease documents, and when the lease manager worker restarts again it's happy.

We should find a way to avoid the error messages. Ideally that would be extracting the lease manager out of the State object, but I don't know if that's practical yet.

Changed in juju:
milestone: 2.3-beta2 → none
Andrew Wilkins (axwalk)
Changed in juju:
assignee: nobody → Andrew Wilkins (axwalk)
milestone: none → 2.3.0
status: Triaged → In Progress
importance: High → Critical
Revision history for this message
Andrew Wilkins (axwalk) wrote :
Changed in juju:
milestone: 2.3.0 → 2.3-beta3
Andrew Wilkins (axwalk)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → 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.