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

Quay 3.7.0 Clair new APP POD can not be ready after reconfigure Quay with config editor

    XMLWordPrintable

Details

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

    Description

      Description:

      This is an issue found about Clair when reconfigure quay with config editor, now after deployed quay with operator, use quay config editor, make some changes(enable build, upload custom certificates, etc), Click reconfigure Quay, waiting for Quay Operator to reconcile the change, the results is new Clair APP POD can't come to ready status, and then killed by Openshift, and new Clair APP POD keeping provisioning and then terminating, refer to the logs of new_clair_app_pod.logs 

      Quay Image: quay-operator-bundle-container-v3.7.0-92

      0s          Normal    Created                        pod/quay370-clair-app-6bf9fc95d8-l9t4m             Created container clair-app
      0s          Normal    Started                        pod/quay370-clair-app-6bf9fc95d8-l9t4m             Started container clair-app
      0s          Normal    ScalingReplicaSet              deployment/quay370-clair-app                       Scaled up replica set quay370-clair-app-6bf9fc95d8 to 5
      0s          Normal    Scheduled                      pod/quay370-clair-app-6bf9fc95d8-xdjb4             Successfully assigned quay370/quay370-clair-app-6bf9fc95d8-xdjb4 to ip-10-0-147-66.us-west-2.compute.internal
      0s          Normal    AddedInterface                 pod/quay370-clair-app-6bf9fc95d8-xdjb4             Add eth0 [10.128.3.242/23] from openshift-sdn
      0s          Normal    Pulled                         pod/quay370-clair-app-6bf9fc95d8-xdjb4             Container image "registry.redhat.io/quay/clair-rhel8@sha256:58c5580f24eef1c29711ef3ee8dba295017897c3e1f59fcac8fa32560bde76fb" already present on machine
      0s          Normal    Created                        pod/quay370-clair-app-6bf9fc95d8-xdjb4             Created container clair-app
      0s          Normal    Started                        pod/quay370-clair-app-6bf9fc95d8-xdjb4             Started container clair-app
      0s          Normal    ComponentsCreationSuccess      quayregistry/quay370                               All objects created/updated successfully
      0s          Normal    Killing                        pod/quay370-clair-app-6bf9fc95d8-gm8r6             Stopping container clair-app
      0s          Normal    Killing                        pod/quay370-clair-app-6bf9fc95d8-l9t4m             Stopping container clair-app
      0s          Normal    Killing                        pod/quay370-clair-app-6bf9fc95d8-xdjb4             Stopping container clair-app
      0s          Normal    Killing                        pod/quay370-clair-app-6bf9fc95d8-xdjb4             Stopping container clair-app 

      Steps:

      1. Deploy Quay with Quay Operator
      2. Login Config editor and make some change, like add new super user, enable build, upload custom SSL Certs, etc
      3. Click Validations
      4. Click Reconfigure Quay
      5. Check the results after Quay Operator reconcile the change

      Expected Results:

      Quay. Mirror, Clair PDO are redeployed by using new configurations, and come to ready status.

      Actual Results:

      Quay. Mirror  PDO are redeployed by using new configurations, and come to ready status. But new Clair APP POD can't come to ready status, after started to running status, then killed by Openshift Cluster.

      Attachments

        Activity

          People

            rmarasch@redhat.com Ricardo Maraschini (Inactive)
            lzha1981 luffy zhang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: