Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-19773

GIT LFS throws "cannot fork to run external filter" error when repository caching on remote agents is enabled

XMLWordPrintable

      Summary

      Source code checkout task throws the below error with LFS enabled GIT repositories when run on a remote agent.

      error: cannot fork to run external filter 
error: external filter  failed

      Steps to Reproduce

      1. Dedicate a remote agent to a plan that has Source code checkout task that is tagged to a GIT LFS repository
      2. Make sure the option 'Enabled repository caching on remote agents' option in the respecive Linked Repository settings page is enabled.
      3. Run the plan

      Expected Results

      The plan executes successfully without any error

      Actual Results

      The below exception is thrown multiple times in the build log file:

      simple	18-Mar-2018 01:15:09	error: cannot run : No such file or directory
simple	18-Mar-2018 01:15:09	error: cannot fork to run external filter 
simple	18-Mar-2018 01:15:09	error: external filter  failed

      Workaround

      Disable Cache by going to Linked Repositories -> Repo -> disable 'Enabled repository caching on remote agents'

      Solution

      Upgrade git to version 2.8

        1. plan-6979585-JOB1-17.log
          12 kB

          Form Name

            [BAM-19773] GIT LFS throws "cannot fork to run external filter" error when repository caching on remote agents is enabled

            Marcin Gardias added a comment - - edited

            I cannot reproduce the issue with git v2.21 and git-lfs v2.4.2. However, the problem is reproducible with git v2.7.1 and git-lfs v2.3.4. Please, make sure you use current version of those tools.

            Update: As far as I can tell, the minimum version of git that doesn't have the problem is 2.8 (tested with 2.8.4)

            Regards

            Marcin Gardias

            Bamboo Development Team

            Marcin Gardias added a comment - - edited I cannot reproduce the issue with git v2.21 and git-lfs v2.4.2. However, the problem is reproducible with git v2.7.1 and git-lfs v2.3.4. Please, make sure you use current version of those tools. Update: As far as I can tell, the minimum version of git that doesn't have the problem is 2.8 (tested with 2.8.4) Regards Marcin Gardias Bamboo Development Team

            Florian Obermayer added a comment -

            Affects 6.7.1, too

            @Pawel @Jeyanthan we tried to clear the affected cache, however it was skipped with following message: 

            Skipping non-existent Git cache '62f17[...]32d1'

            Florian Obermayer added a comment - Affects 6.7.1, too @Pawel @Jeyanthan we tried to clear the affected cache, however it was skipped with following message:  Skipping non-existent Git cache '62f17 [...] 32d1'

            Pawel Skierczynski added a comment -

            Hi yassin.bennaceur
            Can you try clearing the caches from the Overview -> Repository settings -> Manage Caches and tell us if the error still appears in the next subsequent build?

            Pawel Skierczynski added a comment - Hi  yassin.bennaceur Can you try clearing the caches from the  Overview -> Repository settings -> Manage Caches  and tell us if the error still appears in the next subsequent build?

            Yassin Bennaceur added a comment -

            Affects 6.5.0 as well

            Yassin Bennaceur added a comment - Affects 6.5.0 as well

            Jeyanthan I (Inactive) added a comment -

            Hi sergio.batista,
            Can you try clearing the caches from the Overview -> Repository settings -> Manage Caches and tell us if the error still appears in the next subsequent build?

            Jeyanthan I (Inactive) added a comment - Hi sergio.batista , Can you try clearing the caches from the Overview -> Repository settings -> Manage Caches and tell us if the error still appears in the next subsequent build?

            Sergio Batista added a comment -

            also affects 6.4.1

            Sergio Batista added a comment - also affects 6.4.1

              Unassigned Unassigned
              jinbasekaran Jeyanthan I (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: