Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8031

Git resolver upstream - "cannot fork for remote-https: resource unavailable"

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      This change addresses a recent bug in which the git resolver would stop being able to resolve ResolutionRequests with the error "cannot fork() for remote-https: Resource temporarily unavailable". This bug is no longer present and after an update the git-resolver will resume resolving any ResolutionRequests as normal.
      Show
      This change addresses a recent bug in which the git resolver would stop being able to resolve ResolutionRequests with the error "cannot fork() for remote-https: Resource temporarily unavailable". This bug is no longer present and after an update the git-resolver will resume resolving any ResolutionRequests as normal.
    • Bug Fix
    • 5

      Description of problem:

      This error occurs when trying to run the fbc-fips-check-oci-ta task:

      error requesting remote resource: error getting "Git" "dev-release-team-tenant/git-9fa70ea0f01d26756fbb1db383244b6f": error resolving repository: git clone error: Cloning into '/tmp/build-definitions-894456561'... error: cannot fork() for remote-https: Resource temporarily unavailable: exit status 255 

      How reproducible:

      Steps to Reproduce:
      1. create FBC component
      2. watch build
      3. observe error

      This happens currently on rh01 stage. See https://konflux-ui.apps.stone-stg-rh01.l2vh.p1.openshiftapps.com/ns/dev-release-team-tenant/applications/e2eapp-07b82650/pipelineruns/fbc-release-07b82650-on-push-s7hd6/logs?task=fbc-fips-check-oci-ta

       

              rh-ee-athorp Andrew Thorp
              rh-ee-athorp Andrew Thorp
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: