-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
file-integrity-operator-1.3.5, file-integrity-operator-1.3.6
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
I installed the file integrity operator in HCP cluster and created the fileintegrity CR.
$ 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
file-integrity-operator-676dcd4649-r44q8 1/1 Running 2 (4m24s ago) 5m25s
The pods went into CrashLoopBackOff state:
$ oc --kubeconfig hosted-kubeconfig logs aide-example-fileintegrity-2z6xg -n openshift-file-integrity -c check-folder
Directory /etc/kubernetes/static-pod-resources does not exist, exiting.
Probably the file integrity operator is currently not compatible with the HCP clusters.
