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

Clair getting many requests to index non-existant layers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Normal
    • None
    • None
    • quay, quay.io
    • False
    • None
    • False
    • 0

    Description

      We get a lot of these types of errors when attempting to download layers:

      failed to fetch layers: encountered error while fetching a layer: error realizing layer sha256:5293f24e29883796a79a22456877dc4ce8b7a07f2da6151661fe643d38b4f1cd: fetcher: unexpected status code: 404 Not Found (body starts: \"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>sha256/52/5293f24e29883796a79a22456877dc4ce8b7a07f2da6151661fe643d38b4f1cd</Key><RequestId>KNN2YHFGPMW8W55W</RequestId><HostId>P2mR\")
      

      Having checked S3 previously it does indeed look like the key doesn't exist. Previously it seemed like it could be explained away with a race-condition with Quay's GC but it seems to be too frequent for that. Could someone look into this?

      Attachments

        Activity

          People

            Unassigned Unassigned
            jcroslan@redhat.com Joseph Crosland
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: