OSD Prepare pod stuck in CrashLoopBackOff / Error state with, 'Error EEXIST: entity osd.X exists but key does not match' in an OCS 4.X cluster

Solution Verified - Updated -

Issue

  • OSD Prepare pod stuck in CrashLoopBackOff / Error state with, 'Error EEXIST: entity osd.X exists but key does not match' in an OCS 4.X cluster
[2021-10-21 12:55:25,592][ceph_volume.process][INFO  ] Running command: /usr/bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring -i - osd new 8a16-4793-9d55-395d9f4c110e
[2021-10-21 12:55:25,970][ceph_volume.process][INFO  ] stderr Error EEXIST: entity osd.2 exists but key does not match
  • After a node replacement, the OSD Prepare pods are stuck in CrashLoopBackOff / Error state.

Environment

  • Red Hat OpenShift Container Storage 4X

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