etcd fails to start with "failed to read WAL, cannot be repaired"

Problem

  • Master node is in NotReady state as etcd fails to start.

Environment

  • Platform9 Managed Kubernetes - v5.6.0 and Higher

Cause

  • Node filesystem was built with incorrect filesystem for etcd data.

Resolution

  • Rebuild the cluster with supported filesystem.

Additional Information

  • Below error is seen in etcd logs:
Javascript
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard