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

Quay APP POD was failed to start after configure to use AWS S3 Cloud front as backend storage

XMLWordPrintable

      Description:

      This is an issue found when configure quay to use AWS S3 Cloudfront as registry storage, initially with Quay Operator to deploy quay with AWS S3 as registry storage, then use quay config editor to config to use AWS S3 Cloudfront as registry storage, upload AWS Cloudfront Private key, trigger quay redeployment, Quay APP POD was failed to start with error message "FileNotFoundError: [Errno 2] No such file or directory: '/quay-registry/conf/stack/default-cloudfront-signing-key.pem'", see Quay APP POD logs attached.

      Index Image:

      Index image v4.7: brew.registry.redhat.io/rh-osbs/iib-pub-pending:v4.7

      Quay Image:

      oc get pod
      NAME                                         READY   STATUS      RESTARTS   AGE
      quayaws-clair-app-67d5f55c48-c5twj           0/1     Running     0          76s
      quayaws-clair-app-888476569-86d2v            1/1     Running     0          32m
      quayaws-clair-postgres-74745b9ccc-j8tls      1/1     Running     0          44s
      quayaws-quay-app-8649f4c8c4-l64sh            1/1     Running     3          32m
      quayaws-quay-app-cf75d7975-zflb6             0/1     Error       3          78s
      quayaws-quay-config-editor-98f99fdb6-gn5zd   1/1     Running     0          77s
      quayaws-quay-database-f575d658c-8z94l        1/1     Running     0          65s
      quayaws-quay-mirror-fcd588dc9-spr75          0/1     Error       2          37s
      quayaws-quay-postgres-init-rtpbq             0/1     Completed   0          76s
      quayaws-quay-redis-7fb8757ff4-cldwg          1/1     Running     0          76s
      
      oc get pod quayaws-quay-app-cf75d7975-zflb6 -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/quay/quay-rhel8@sha256:7bb8b18eab97d2ca2814322cb63b7c45b810ccbd0a2d03424cc06a6d7bc463ba"
      

      Quay Operator Image:

      oc get pod quay-operator.v3.4.2-78bc4fdf76-8v778 -n openshift-operators -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/quay/quay-operator-rhel8@sha256:bf29ea38bd88f48377b91d6d56d0db7695ecbf4a954cdb544c525c50ad8ed382"
      

      Configure Quay to use AWS Cloudfront S3 as registry storage:

      Quay config editor

      Steps:

      1. Deploy Quay 3.4.2 with V3.4.2 TNG Operator on AWS using AWS S3 object Storage
      2. Open Quay config editor and change backend storage to AWS S3 + Cloudfront
      3. Input valid configurations, and upload AWS S3 Cloudfront Private Key
      4. Click "Validate Configurations Change"
      5. Click "Reconfigure Quay"
      6. Check new Quay APP POD status

      Expected Results:

      New Quay APP POD come to ready status.

      Actual Results:

      New Quay APP POD was failed to start with error message "FileNotFoundError: [Errno 2] No such file or directory: '/quay-registry/conf/stack/default-cloudfront-signing-key.pem'""

              jonathankingfc Jonathan King
              lzha1981 luffy zhang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: