Compliance related pods are in "Not Ready" and "Initializing" state

Solution Verified - Updated -

Issue

The resultServer pods (-rs) are scheduled in masters and fail to mount the needed volumes and show events like these:

MountVolume.MountDevice failed for volume "pvc-00000000-1111-2222-3333-444444444444" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name openshift-storage.rbd.csi.ceph.com not found in the list of registered CSI drivers'

Unable to attach or mount volumes: unmounted volumes=[arfreports], unattached volumes=[arfreports tls resultserver-token-xxxxx]: timed out waiting for the condition

Specified in the deployment definition of these pods is the nodeSelector hard-coded to masters:

  nodeSelector:
    node-role.kubernetes.io/master: ""

Any try to modify the nodeSelector will be reverted when a configuration sync of the operator pod is triggered (eg.: the pod is killed, updated or moved to another host) rising the same problem again.

Environment

  • OpenShift Container Platform 4.6+
  • Compliance operator installed
  • OpenShift Container Storage (OCS) installed

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