Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-3410

Failed to install File Integrity Operator on Hypershift guest cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.12
    • File Integrity Operator
    • None
    • Important
    • None
    • CMP Sprint 65, CMP Sprint 66, CMP Sprint 67, CMP Sprint 68, CMP Sprint 69, CMP Sprint 70, CMP Sprint 71, CMP Sprint 72, CMP Sprint 73, CMP Sprint 74, CMP Sprint 75
    • 11
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Failed to install File Integrity Operator on Hypershift guest cluster due to "4 node(s) didn't match Pod's node affinity/selector".

       

      $ 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.

      Version-Release number of selected component (if applicable):

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

      How reproducible:

      Always

      Steps to Reproduce:

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

      Actual results:

      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".

      Expected results:

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

      Additional info:

       

              wenshen@redhat.com Vincent Shen
              xiyuan@redhat.com Xiaojie Yuan
              Xiaojie Yuan Xiaojie Yuan
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: