The fileintergrity pod is in Init:CrashLoopBackOff state in HCP cluster in RHOCP 4

Solution Verified - Updated -

Issue

  • File integrity operator pods are in Init:CrashLoopBackOff state in HCP clusters:

    $ oc --kubeconfig  hosted-kubeconfig get pods -n openshift-file-integrity

NAME                                       READY   STATUS                  RESTARTS        AGE
aide-example-fileintegrity-2z6xg           0/1     Init:CrashLoopBackOff   4 (90s ago)     3m4s
aide-example-fileintegrity-rmqwj           0/1     Init:CrashLoopBackOff   4 (87s ago)     3m4s

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4
  • Hosted Control Planes (HCP) / Hypershift

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