$ oc project openshift-file-integrity
Now using project "openshift-file-integrity" on server "https://a536b33ca207f4f2dbd755d460e0778d-c9ca9fea9e74415b.elb.us-east-2.amazonaws.com:6443".
$ oc get ip
NAME            CSV                               APPROVAL    APPROVED
install-7qzr6   file-integrity-operator.v0.1.30   Automatic   true
$ oc get csv -w
NAME                              DISPLAY                   VERSION   REPLACES   PHASE
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Pending
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Pending
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               InstallReady
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
...
$ oc get csv -w
NAME                              DISPLAY                   VERSION   REPLACES   PHASE
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Failed
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Pending
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               InstallReady
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
file-integrity-operator.v0.1.30   File Integrity Operator   0.1.30               Installing
^C
$ oc get pod
NAME                                       READY   STATUS    RESTARTS   AGE
file-integrity-operator-6cd76cdc65-fkdjl   0/1     Pending   0          9m47s
$ oc get event
LAST SEEN   TYPE      REASON                OBJECT                                                  MESSAGE
9m56s       Warning   FailedScheduling      pod/file-integrity-operator-6cd76cdc65-fkdjl            0/4 nodes are available: 4 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.
4m54s       Normal    NotTriggerScaleUp     pod/file-integrity-operator-6cd76cdc65-fkdjl            pod didn't trigger scale-up:
4m46s       Warning   FailedScheduling      pod/file-integrity-operator-6cd76cdc65-fkdjl            0/4 nodes are available: 4 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.
9m56s       Normal    SuccessfulCreate      replicaset/file-integrity-operator-6cd76cdc65           Created pod: file-integrity-operator-6cd76cdc65-fkdjl
9m56s       Normal    ScalingReplicaSet     deployment/file-integrity-operator                      Scaled up replica set file-integrity-operator-6cd76cdc65 to 1
9m59s       Normal    RequirementsUnknown   clusterserviceversion/file-integrity-operator.v0.1.30   requirements not yet checked
9m59s       Normal    RequirementsNotMet    clusterserviceversion/file-integrity-operator.v0.1.30   one or more requirements couldn't be found
4m56s       Normal    AllRequirementsMet    clusterserviceversion/file-integrity-operator.v0.1.30   all requirements found, attempting install
4m56s       Normal    InstallSucceeded      clusterserviceversion/file-integrity-operator.v0.1.30   waiting for install components to report healthy
4m56s       Normal    InstallWaiting        clusterserviceversion/file-integrity-operator.v0.1.30   installing: waiting for deployment file-integrity-operator to become ready: waiting for spec update of deployment "file-integrity-operator" to be observed...
4m56s       Normal    InstallWaiting        clusterserviceversion/file-integrity-operator.v0.1.30   installing: waiting for deployment file-integrity-operator to become ready: deployment "file-integrity-operator" not available: Deployment does not have minimum availability.
4m57s       Warning   InstallCheckFailed    clusterserviceversion/file-integrity-operator.v0.1.30   install timeout
4m57s       Normal    NeedsReinstall        clusterserviceversion/file-integrity-operator.v0.1.30   installing: waiting for deployment file-integrity-operator to become ready: deployment "file-integrity-operator" not available: Deployment does not have minimum availability.

4.12.0-0.nightly-2022-11-07-181244 + file-integrity-operator.v0.1.30

Always

1.Install File Integrity Operator on Hypershift guest cluster 2.

The file file-integrity-operator pod will be stuck at "Pending" status due to "4 node(s) didn't match Pod's node affinity/selector".

The File Integrity Operator on Hypershift guest cluster could be installed successfully.