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

s2i-java task fails with /usr/libexec/s2i/assemble: No such file or directory

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Fixed the location for IMAGE_SCRIPTS_URL in the s2i-java task.
      Previously, the task referenced `/usr/libexec/s2i/assemble` as the default path for S2I scripts, which caused failures on the s2i-java task. This update changes the default path to `/usr/local/s2i` for s2i-java task, while other s2i tasks (e.g., for Go or .NET) continue to use the original path.
      Show
      Fixed the location for IMAGE_SCRIPTS_URL in the s2i-java task. Previously, the task referenced `/usr/libexec/s2i/assemble` as the default path for S2I scripts, which caused failures on the s2i-java task. This update changes the default path to `/usr/local/s2i` for s2i-java task, while other s2i tasks (e.g., for Go or .NET) continue to use the original path.
    • 5
    • Pipelines Sprint Pioneers 25, Pipelines Sprint Pioneers 26, Pipelines Sprint Pioneers 27, Pipelines Sprint Pioneers 28

      Description of problem:

      When using the pipeline builder and the default value for the parameter IMAGE_SCRIPTS_URL is used in the s2i-java task it fails with the error message "/usr/libexec/s2i/assemble: No such file or directory". The problem seems to be have been introduced in the 1.17 release and does not reproduce in prior versions.

      Workaround:

      Set value for the IMAGE_SCRIPTS_URL parameter to 
      image:///usr/local/s2i
       
      This problem also reproduces when using the "import from Git" to generate a pipeline for a Java application.
       
      The s2i-java task fails with these errors:
       
      2025-03-13T14:15:29.647226364Z STEP 7/8: RUN /usr/libexec/s2i/assemble
      2025-03-13T14:15:29.754545917Z /bin/sh: /usr/libexec/s2i/assemble: No such file or directory
      2025-03-13T14:15:29.754744648Z subprocess exited with status 127
      2025-03-13T14:15:29.757103876Z subprocess exited with status 127
      2025-03-13T14:15:29.867469049Z Error: building at STEP "RUN /usr/libexec/s2i/assemble": exit status 127

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Create a new pipeline in the OpenShift console
      2. Add a workspace and name it shared-workspace
      3. Add a git-clone task and set the following parameters
        URL = https://github.com/quarkusio/quarkus-quickstarts 
        output = shared-workspace
      4. Add a s2i-java task and set the parameters 
        IMAGE = 
        image-registry.openshift-image-registry.svc:5000/PROJECT-NAME/quarkus-quickstarts
        CONTEXT = getting-started
        source = shared-workspace
      5. Click Create
      6. Start the pipeline

      Actual results:

      The execution of the pipeline fails with the error:

      STEP 7/8: RUN /usr/libexec/s2i/assemble
      /bin/sh: /usr/libexec/s2i/assemble: No such file or directory
      subprocess exited with status 127
      subprocess exited with status 127
      Error: building at STEP "RUN /usr/libexec/s2i/assemble": exit status 127

      Expected results:

      The image metadata should be picked up and the value for the parameter IMAGE_SCRIPTS_URL should be set to a correct value.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      A correct default value for the parameter IMAGE_SCRIPTS_URL should be set and the task should complete successfully 

      Definition of Done:

      When the default value for the IMAGE_SCRIPTS_URL in the s2i-java task can be used

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      See attached log file.

       *

        1. s2i-java.log
          5 kB
          Martin Östmark

              rh-ee-pbheeman Pavan Mandayam Bheeman
              mostmark@redhat.com Martin Östmark
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: