Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-23961

console-acm-213 on-push builds are failing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • ACM 2.13.5
    • ACM 2.13.5
    • Console
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • ACM Console Train 32 - 1
    • Critical
    • None

      Description of problem:

      Images are old for console-acm-213 - a little investigation shows the on-push pipeline is having a problem.  

      Example build failure: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/crt-redhat-acm-tenant/applications/release-acm-213/pipelineruns/console-acm-213-on-push-q75gm

      The problem in this case is the arm64 build fails with this error:

      npm error code ENOMEM
      npm error syscall spawn
      npm error errno -12
      npm error spawn ENOMEM
      npm error A complete log of this run can be found in: /opt/app-root/src/.npm/_logs/2025-09-09T15_20_31_474Z-debug-0.log
      subprocess exited with status 244
      subprocess exited with status 244
      Error: building at STEP "RUN . /cachi2/cachi2.env &&     cd frontend && npm ci --legacy-peer-deps --unsafe-perm": exit status 244
      step-prepare-sboms :-
      2025/09/09 15:23:06 Skipping step because a previous step failed

      There are many other on-push failures, guessing they may be the same.

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

      How reproducible:

      Steps to Reproduce:

      1.  
      2.  
      3. ...

      Actual results:

      Expected results:

      Additional info:

              rbrunopi Randy Bruno-Piverger
              gparvin-redhat Gus Parvin
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: