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

Clair-v4 DB upgrade scanning issues.

XMLWordPrintable

    • Strategic Product Work
    • False
    • None
    • False
    • Compatibility/Configuration, User Experience
    • Hide
      {"log":"{\"level\":\"debug\",\"component\":\"httptransport/New\",\"request_id\":\"245623f5861cff56\",\"code\":500,\"error\":\"failed to start scan: failed to fetch layers: encountered error while fetching a layer: error realizing layer sha256:0c186e733db598968d62afa4aa97d922462248c2d61dbbf9b3b1b14bb1e9680e: fetcher: unexpected status code: 400 Bad Request (body starts: \\\"\u003c?xml version=\\\\\\\"1.0\\\\\\\" encoding=\\\\\\\"UTF-8\\\\\\\"?\u003e\\\\n\u003cError\u003e\u003cCode\u003eAuthorizationQueryParametersError\u003c/Code\u003e\u003cMessage\u003eError parsing the X-Amz-Credential parameter; the region 'us-east-1' is wrong; expecting 'us-west-2'\u003c/Message\u003e\u003cRegion\u003eus-west-2\u003c/Region\u003e\u003cRequestId\u003eKD38M7GE\\\")\",\"time\":\"2025-02-05T17:12:08Z\",\"message\":\"http error response\"}\n","stream":"stderr","time":"2025-02-05T17:12:08.14576163Z"}
      

      looks like it is getting us-east-1 from boto but the storage config has us-west-2:

      DISTRIBUTED_STORAGE_CONFIG:
        s3Storage:
          - CloudFrontedS3Storage
          - host: s3-us-west-2.amazonaws.com
            s3_access_key: AKIA2U3SAW7D33SMXZMY
            s3_secret_key: XXXXXXXXXXXXXXXXXXXXXXXXX
            s3_bucket: dckr-reg-files-development
            s3_region: us-west-2
            storage_path: /datastorage/registry
            cloudfront_distribution_domain: d2ajgav4lbdz56.cloudfront.net/datastorage/registry
            cloudfront_key_id: K1L2G0PKWXJ5T0
            cloudfront_privatekey_filename: cloudfront-signing-key.pem
            cloudfront_distribution_org_overrides: {}
      
      Show
      { "log" : "{\" level\ ":\" debug\ ",\" component\ ":\" httptransport/New\ ",\" request_id\ ":\" 245623f5861cff56\ ",\" code\ ":500,\" error\ ":\" failed to start scan: failed to fetch layers: encountered error while fetching a layer: error realizing layer sha256:0c186e733db598968d62afa4aa97d922462248c2d61dbbf9b3b1b14bb1e9680e: fetcher: unexpected status code: 400 Bad Request (body starts: \\\ "\u003c?xml version=\\\\\\\" 1.0\\\\\\\ " encoding=\\\\\\\" UTF-8\\\\\\\ "?\u003e\\\\n\u003cError\u003e\u003cCode\u003eAuthorizationQueryParametersError\u003c/Code\u003e\u003cMessage\u003eError parsing the X-Amz-Credential parameter; the region 'us-east-1' is wrong; expecting 'us-west-2' \u003c/Message\u003e\u003cRegion\u003eus-west-2\u003c/Region\u003e\u003cRequestId\u003eKD38M7GE\\\" )\ ",\" time\ ":\" 2025-02-05T17:12:08Z\ ",\" message\ ":\" http error response\ "}\n" , "stream" : "stderr" , "time" : "2025-02-05T17:12:08.14576163Z" } looks like it is getting us-east-1 from boto but the storage config has us-west-2: DISTRIBUTED_STORAGE_CONFIG: s3Storage: - CloudFrontedS3Storage - host: s3-us-west-2.amazonaws.com s3_access_key: AKIA2U3SAW7D33SMXZMY s3_secret_key: XXXXXXXXXXXXXXXXXXXXXXXXX s3_bucket: dckr-reg-files-development s3_region: us-west-2 storage_path: /datastorage/registry cloudfront_distribution_domain: d2ajgav4lbdz56.cloudfront.net/datastorage/registry cloudfront_key_id: K1L2G0PKWXJ5T0 cloudfront_privatekey_filename: cloudfront-signing-key.pem cloudfront_distribution_org_overrides: {}
    • Important
    • Customer Reported

      We've updated our AWS RDS managed Clair v4 PostGres SQL DB from 12.19 to 15.7 
      The DB upgrade went ahead without problem but we see issues when trying to scan new images. 
      The images appear to be stuck in the '...Queued` state and appear to be unable to progress to generating a bug report. 
      
      I've uploaded a image called : clair-test:bitnami_memcached as a reference and I'm including all the relevant config debug logs.
      
      Our version of Quay is v3.10.6 and Clair-v4 is v3.10.6
      

              bcaton@redhat.com Brandon Caton
              dshoemak@redhat.com Daniel Shoemaker
              Sean Zhao Sean Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: