Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-23408

Error occurs during a build with a buildconfig from a git repo that has Nexus LFS files inside

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done-Errata
    • Normal
    • None
    • 4.12.z
    • Build
    • None
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-19358. The following is the description of the original issue:

      Description of problem:

      When attempting to perform a build using a buildconfig from a Git repository that contains Nexus LFS files, the build process encounters an error. The error message received is as follows:
      
      I0915 14:59:38.735592 1 repository.go:533] Error executing command: exit status 128
      error: Cloning into '/tmp/build/inputs'...
      Updating files: 57% (13174/23013)...
      fatal: the remote end hung up unexpectedly
      error: git-lfs filter-process died of signal 9
      
      This issue was not present in OCP versions prior to 4.12.24, where git-lfs was introduced for the first time.
      
      Also this issue does not happen with a GitHub LFS endpoint, only with Nexus LFS.

      Version-Release number of selected component (if applicable):

      4.12.24

      How reproducible:

      Always

      Steps to Reproduce:

      Reproducer not yet available.

      Actual results:

      Builds fail with 'error: git-lfs filter-process died of signal 9'

      Expected results:

      The build should work.

      Additional info:

      - OCP version 4.12.24 introduced git-lfs, and prior versions did not have git-lfs functionality.
        - Related Bug: [OCPBUGS-15643 - Can't use git lfs in BuildConfig git source with strategy Docker](https://issues.redhat.com/browse/OCPBUGS-15643)
        - Red Hat Bug Advisory: [RHBA-2023:3977](https://access.redhat.com/errata/RHBA-2023:3977)
        - GitHub Pull Request: [OCPBUGS-15643: Add the git-lfs package #353](https://github.com/openshift/builder/pull/353)
      
      - This build process previously functioned correctly in OCP 4.10 but encountered issues after upgrading to OCP 4.12.
      
      - Attempting to utilize the environment variable `GIT_LFS_SKIP_SMUDGE` to ignore LFS during the clone process is not possible in BuildConfigs.
      
      - A mitigation strategy involves creating a new branch in the Git repo without any LFS files.
      
      - The exact setup for a reproducer is currently unclear. (i.e., it's not just about having a git repo with LFS files inside). It looks like it happens with Nexus LFS, and not with a GitHub LFS endpoint.
      
      

      Attachments

        Issue Links

          Activity

            People

              cdaley Corey Daley
              openshift-crt-jira-prow OpenShift Prow Bot
              Corey Daley Corey Daley
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: