rook-ceph-osd-prepare pods launched when storage nodes are restarted or the ODF operator is updated

Solution Verified - Updated -

Issue

  • When infrastructure storage nodes are restarted or the ODF operator is updated, rook-ceph-osd-prepare pods are launched again.

  • The cluster is configured with X number of OSDs and all X OSDs are up and running.

# ceph status
  cluster:
    id:     xxxx9a3e-d6xx-xxbb-xx8a-cxxxxxxxxxxx
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum a,b,c (age 23h)
    mgr: a(active, since 23h)
    mds: 1/1 daemons up, 1 hot standby
    osd: 3 osds: 3 up (since 23h), 3 in (since 3w)  <-----------------
    rgw: 1 daemon active (1 hosts, 1 zones)
  • Event logs the osd-prepare pods are waiting to be scheduled.
77s         Normal    WaitForPodScheduled      persistentvolumeclaim/ocs-deviceset-localblock-0-data-xxxxxx       waiting for pod rook-ceph-osd-prepare-fdb86af17a1b3aa506a8497b404f8f43-579rv to be scheduled
77s         Normal    WaitForPodScheduled      persistentvolumeclaim/ocs-deviceset-localblock-0-data-xxxxxx       waiting for pod rook-ceph-osd-prepare-185e4e0390d6ef15e70111da89cb13e9-qsnp6 to be scheduled
77s         Normal    WaitForPodScheduled      persistentvolumeclaim/ocs-deviceset-localblock-0-data-xxxxxx       waiting for pod rook-ceph-osd-prepare-609f00654085664de39126122eeb1a48-fssdk to be scheduled

Environment

  • OpenShift Data Foundation 4.12
  • Red Hat Ceph Storage 5.x

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