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

Compliance Operator failed to install on guest cluster of HyperShift

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • 4.12.0
    • Compliance Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When trying to install Compliance Operator on guest cluster of HyperShift with redhat-operators catalogsource, the installation failed:

       

      $ oc get csv
      NAME                          DISPLAY               VERSION   REPLACES   PHASE
      compliance-operator.v0.1.53   Compliance Operator   0.1.53               Failed
      $ oc get event
      LAST SEEN   TYPE      REASON                OBJECT                                              MESSAGE
      17m         Warning   FailedScheduling      pod/compliance-operator-54d7c8f758-h79d8            0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
      2m29s       Normal    NotTriggerScaleUp     pod/compliance-operator-54d7c8f758-h79d8            pod didn't trigger scale-up:
      12m         Warning   FailedScheduling      pod/compliance-operator-54d7c8f758-h79d8            0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
      

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

      compliance-operator.v0.1.53 clusterversion: 4.12.0-0.nightly-2022-10-15-094115

      How reproducible:

      Always

      Steps to Reproduce:

      install Compliance Operator on guest cluster of HyperShift with redhat-operators catalogsource

      Actual results:

      Installation failed.

       

      $ oc get node
      NAME                                         STATUS   ROLES    AGE     VERSION
      ip-10-0-133-165.us-east-2.compute.internal   Ready    worker   5h19m   v1.25.2+5bf2e1f
      ip-10-0-133-249.us-east-2.compute.internal   Ready    worker   5h19m   v1.25.2+5bf2e1f
      $ oc get ip
      NAME            CSV                           APPROVAL    APPROVED
      install-ttrjh   compliance-operator.v0.1.53   Automatic   true
      $ oc get csv
      NAME                          DISPLAY               VERSION   REPLACES   PHASE
      compliance-operator.v0.1.53   Compliance Operator   0.1.53               Failed
      $ oc get pod
      NAME                                   READY   STATUS    RESTARTS   AGE
      compliance-operator-54d7c8f758-h79d8   0/1     Pending   0          17m
      $ oc get event
      LAST SEEN   TYPE      REASON                OBJECT                                              MESSAGE
      17m         Warning   FailedScheduling      pod/compliance-operator-54d7c8f758-h79d8            0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
      2m29s       Normal    NotTriggerScaleUp     pod/compliance-operator-54d7c8f758-h79d8            pod didn't trigger scale-up:
      12m         Warning   FailedScheduling      pod/compliance-operator-54d7c8f758-h79d8            0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
      17m         Normal    SuccessfulCreate      replicaset/compliance-operator-54d7c8f758           Created pod: compliance-operator-54d7c8f758-h79d8
      17m         Normal    ScalingReplicaSet     deployment/compliance-operator                      Scaled up replica set compliance-operator-54d7c8f758 to 1
      17m         Normal    RequirementsUnknown   clusterserviceversion/compliance-operator.v0.1.53   requirements not yet checked
      17m         Normal    RequirementsNotMet    clusterserviceversion/compliance-operator.v0.1.53   one or more requirements couldn't be found
      12m         Normal    AllRequirementsMet    clusterserviceversion/compliance-operator.v0.1.53   all requirements found, attempting install
      12m         Normal    InstallSucceeded      clusterserviceversion/compliance-operator.v0.1.53   waiting for install components to report healthy
      12m         Normal    InstallWaiting        clusterserviceversion/compliance-operator.v0.1.53   installing: waiting for deployment compliance-operator to become ready: waiting for spec update of deployment "compliance-operator" to be observed...
      12m         Normal    InstallWaiting        clusterserviceversion/compliance-operator.v0.1.53   installing: waiting for deployment compliance-operator to become ready: deployment "compliance-operator" not available: Deployment does not have minimum availability.
      12m         Warning   InstallCheckFailed    clusterserviceversion/compliance-operator.v0.1.53   install timeout
      12m         Normal    NeedsReinstall        clusterserviceversion/compliance-operator.v0.1.53   installing: waiting for deployment compliance-operator to become ready: deployment "compliance-operator" not available: Deployment does not have minimum availability.
      7m32s       Warning   InstallCheckFailed    clusterserviceversion/compliance-operator.v0.1.53   install failed: deployment compliance-operator not ready before timeout: deployment "compliance-operator" exceeded its progress deadline
      

      Expected results:

      Installation succeeded.

      Additional info:

       

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

                Created:
                Updated:
                Resolved: