Heketi pod fails to start if heketidb is inconsistent

Solution Verified - Updated -

Issue

Heketi pod fails to start up after shutdown or crash.
Below errors are observed.

/src/github.com/heketi/heketi/apps/glusterfs/dbcommon.go:121: failed to upgrade db for brick entries :id not found。
/src/github.com/heketi/heketi/apps/glusterfs/app.go:131: unable to upgrade changes。
/src/github.com/heketi/heketi/apps/glusterfs/app.go:139: id not found

Environment

  • Openshift Container Platform 3.6
  • Heketi 5.x
  • Openshift Container Storage 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content