Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-3430

Clair pod can not be running in quay v3.7.0-37 build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • quay-v3.7.0
    • clair, quay-operator
    • None
    • 0

      Description of problem:

      After deploying quay on OCP 4.9 with v3.7.0-37 build, the Clair pods go to `CrashLoopBackOff`.

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

       

      $ oc get $(oc get pod -l name=quay-operator-alm-owned -o name -n quay-enterprise) -o jsonpath='{.spec.containers[0].image}' -n quay-enterprise
      registry.redhat.io/quay/quay-operator-rhel8@sha256:870b5211cb720974d7386ddc0906086b217c49970e099b504d5b9fa21684160d
      
      $ oc get quayregistry -o jsonpath='{.items[0].status.currentVersion}'  -n quay-enterprise
      3.7.0

       

      How reproducible:

      always

      Steps to Reproduce:
      1.  Deploy quay pre-release  version as normal .

      Actual results:

      The clair pods go to `CrashLoopBackOff`.

      Expected results:

      The clair pods run successfully.

      Additional info:

       $ oc get pod
      NAME                                               READY   STATUS             RESTARTS        AGE
      quay-operator.v3.7.0-7d99c94fcf-fmzbz              1/1     Running            0               3h14m
      quayregistry-clair-app-5779579475-qwk6c            0/1     CrashLoopBackOff   13 (5m1s ago)   46m
      quayregistry-clair-app-7cbf586b47-llt9b            0/1     CrashLoopBackOff   17 (19s ago)    62m
      quayregistry-clair-app-7cbf586b47-prjcr            0/1     CrashLoopBackOff   16 (5m9s ago)   62m
      quayregistry-clair-postgres-749b49ffb5-4brdg       1/1     Running            1 (62m ago)     62m
      quayregistry-quay-app-f579dbc59-jbk89              1/1     Running            0               46m
      quayregistry-quay-app-f579dbc59-nm2mg              1/1     Running            0               45m
      quayregistry-quay-app-upgrade--1-qrsth             0/1     Completed          0               62m
      quayregistry-quay-config-editor-559fddb4c7-gq2lm   1/1     Running            0               46m
      quayregistry-quay-database-659d8bdc68-qxw2m        1/1     Running            0               62m
      quayregistry-quay-mirror-598bbb8c67-72bbj          1/1     Running            0               46m
      quayregistry-quay-mirror-598bbb8c67-v6p28          1/1     Running            0               46m
      quayregistry-quay-redis-6cbd47fd59-wn4xh           1/1     Running            0               62m

       

      $ oc describe pod  quayregistry-clair-app-7cbf586b47-prjcr 
      Name:         quayregistry-clair-app-7cbf586b47-prjcr
      .....
      Events:
        Type     Reason          Age                   From                                                 Message
        ----     ------          ----                  ----                                                 -------
        Normal   Scheduled       3m8s                                                                       Successfully assigned quay-enterprise/quayregistry-clair-app-7cbf586b47-prjcr to ip-10-0-160-173.us-east-2.compute.internal
        Normal   AddedInterface  3m6s                  multus                                               Add eth0 [10.131.0.26/23] from openshift-sdn
        Normal   Pulled          2m13s (x4 over 3m6s)  kubelet, ip-10-0-160-173.us-east-2.compute.internal  Container image "registry.redhat.io/quay/clair-rhel8@sha256:77d46e69bdd21bd63cb815f9a38d45ce09818f86f55a8a6612b3e709e7592ade" already present on machine
        Normal   Created         2m12s (x4 over 3m6s)  kubelet, ip-10-0-160-173.us-east-2.compute.internal  Created container clair-app
        Normal   Started         2m12s (x4 over 3m6s)  kubelet, ip-10-0-160-173.us-east-2.compute.internal  Started container clair-app
        Warning  BackOff         2m7s (x13 over 3m4s)  kubelet, ip-10-0-160-173.us-east-2.compute.internal  Back-off restarting failed container
      

       

      $ oc logs quayregistry-clair-app-7cbf586b47-llt9b 
      2022/03/18 05:35:12 failed to decode yaml config: unknown log level "0"

            rhwhu Weihua Hu
            rhwhu Weihua Hu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: