Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-21322

Lower Missing Manifest log message from ERROR level

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done
    • Priority: 4 - Normal
    • Resolution: Done
    • Affects Version/s: 6.17.0
    • Fix Version/s: 6.21.0, 7.7.0
    • Component/s: Logging
    • Labels:
      None

      Description

      We have a virtual Docker repository that includes both our local Docker repo and several remote Docker registries.

      We recently upgraded to 6.17.0 and started seeing ERROR logs when requesting docker images that doesn't exist in either the local or the remote repos.

      2020-02-19 20:19:24,836 [http-nio-8081-exec-5] [ERROR] (o.a.a.d.r.v.DockerV2RemoteRepoHandler:464) - Missing Manifest from dockerhub 'v2/nemesis/suite_runner/test_runner/manifests/0.0.24' not found at dockerhub:nemesis/suite_runner/test_runner/0.0.24/list.manifest.json
      

      The current log level is ERROR but I would argue that there is nothing erounous about a missing manifest for a non existing docker image. It's the client that did something wrong, requesting a non existing image, which shouldn't casuse an ERROR message on the server.

       

      I expect that these logs are lowered from ERROR to a sensible loglevel, like WARNING or INFO.

        Attachments

          Activity

            People

            Assignee:
            andreik Andrei Komarov
            Reporter:
            stefanga Stefan Gangefors
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Sync Status

                Connection: RTFACT Sync
                RTMID-21322 -
                SYNCHRONIZED
                • Last Sync Date: