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

Edge Node smart repository behaviour

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Location:
      External

      Description

      Feature description: Able to successfully download the artifacts that exist under the smart remote cache repository of the Edge Node instance when the connection to the source Artifactory instance is lost. 

      What is the expected behavior? it is very important to understand what the customer is trying to achieve and why

      When we have a smart remote repository at the Edge node instance which is pointing to the source Artifactory when the source Artifactory instance is down when downloading any packages through UI that exists under the Remote Cache repository of the Edge node instance we will get 403 error with message Upstream instance is not Artifactory with Edge license. This is due to the Edge instance trying to verify that this is indeed a Smart Remote repository against the URL and failing with 403 when the source instance is down.

       

      This feature is to allow the edge node to continue functioning as a smart remote repository in the absence of the source Artifactory's instance. 

      Possible workaround: No workaround.

        Attachments

          Activity

              People

              Assignee:
              Unassigned
              Reporter:
              pavang Pavan Gonugunta
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Sync Status

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