Node.js v24 Segmentation Faults During npm Global Installs in Dell VSI (Virtual Storage Integrator) OVA on VMware Photon OS 5.0 (Build b9d98344d)

[murugan-ganesan]

Describe the bug

We are observing consistent segmentation faults when using Node.js v24.14.0 on VMware Photon OS 5.0(Build b9d9834), specifically during npm install -g (global package installation) operations.

Request
We are seeking guidance on:

Official support stance for Node.js v24 on Photon OS 5.0
Recommended approach for running Node.js applications that require global tooling
Whether a Photon‑compatible Node.js LTS build or alternative packaging strategy is planned

Reproduction steps

1.while deploy OVA , we have faced challenges on node_module depedency download package has issue.
2.During jenkins
3.
4. During OVA creation using script.sh, the following command is executed, and it throws an exception.
#Update all software on the system
tdnf update -y
#Install the necessary packages for our code
tdnf install -y python3-pip unzip sshpass nodejs tar
#Install the nodejs library forever for iapi-maintaince-util
npm install forever -g

Expected behavior

Photon OS 5.0 started picking node js 24 also should all to support node modules download without any issue.

Additional context

https://broadcomcms-software.wolkenservicedesk.com/wolken-support/mycases/request-details?requestId=36873117 we have open ticket for DCPN also worked with the support team .

1. Photon OS Support: As previously communicated, the general support team handles only break/fix issues and does not provide support for Photon OS related issues. The process for raising break/fix cases remains unchanged.
2. Automation, SDK, and API Issues: For assistance with automation, SDK, or API-related requests and issues, please open a case directly with the VCF SDK/API support team.
   o How to Open a SDK Support case: Follow the instructions in this Knowledge Base article: https://knowledge.broadcom.com/external/article/436447 [knowledge.broadcom.com]
   o Supported SDK / API Matrix: Our supported matrix is available here: https://knowledge.broadcom.com/external/article/310445/ [knowledge.broadcom.com]

[murugan-ganesan]

We have a workaround to use Node.js version 22, which is compatible with Photon OS 5.0. Below is the script configuration. Please review the script and provide feedback on this workaround, including whether there are any potential impacts.

#Update all software on the system
tdnf update -y

#Install the necessary packages for our code
tdnf install -y python3-pip unzip sshpass tar

#Install Node.js v22.22.0 from nodejs.org to fix segfault issue with Photon OS 5.0 default Node.js v24
NODE_VERSION="v22.22.0"
curl -L "https://nodejs.org/dist/${NODE_VERSION}/node-${NODE_VERSION}-linux-x64.tar.xz" -o /tmp/node22.tar.xz
tar -xf /tmp/node22.tar.xz -C /usr/local/ --strip-components=1
rm /tmp/node22.tar.xz
npm install -g npm@10.9.4

[dcasota]

Hi,

The segfaults on npm install [-g] are caused by V8 (inside Node.js) crashing when the binary is compiled with the compiler’s Identical Code Folding (ICF) optimisation enabled — a long-standing upstream issue tracked at nodejs/node#47865.

The nodejs-24.14.0-2.ph5 (or pre-fix 24.14.1-1) RPM pulled by your OVA build was compiled before the workaround. The Photon team already rebuilt the package as nodejs-24.14.1-2.ph5 on 22 Apr 2026, adding -fno-ipa-icf to CFLAGS/CXXFLAGS (see the %build section and changelog in SPECS/nodejs/nodejs.spec on the 5.0 branch).

For the Dell VSI OVA, refresh the build pipeline so tdnf pulls nodejs-24.14.1-2.ph5 (or newer) before running npm install forever -g and the subsequent npm install. This should resolve the crashes.

The pip3 ModuleNotFoundError and vsi-proxy Docker Compose add-host empty-IP errors visible in the same logs are unrelated and will need separate fixes.

[murugan-ganesan]

@dcasota thanks for your response
Regarding this, do we need to make any code changes to the current script file, or will it continue to work without any code changes for new OVA creation?

[murugan-ganesan]

Below the script we are using, is there any code change need on this specific to the node js ?
#Update all software on the system
tdnf update -y

#Install the necessary packages for our code
tdnf install -y python3-pip unzip sshpass nodejs tar

#Install the nodejs library forever for iapi-maintaince-util
npm install forever -g

#Install VMware's vCenter Python bindings
pip3 install --trusted-host pypi.org pyvmomi

#Install Python OpenSSL bindings so we can read the server thumbprint
pip3 install --trusted-host pypi.org pyopenssl

#Upgrade certifi to resolve "Python Library Certifi < 2024.07.04 Untrusted Root Certificate" issue
pip3 install --upgrade certifi==2024.8.30

#Install network-config-manager
tdnf install -y network-config-manager

[dcasota]

First, thank you for the clear report.

I do not know the side effects of downgrading to Node.js 22. Additionally, I do not know the side effects when users on the pre-fix nodejs-24.14.0-2.ph5 resolve the segfaults by running own changes to receive the corrected nodejs-24.14.1-2.ph5 package . In my optinion, the Dell appliance team will communicate their chosen path forward, including any validation or next steps. That's for sure the safe path.

[tapakund]

@murugan-ganesan did you try with latest nodejs-24.14.1-2.ph5?

[murugan-ganesan]

@tapakund we have triggered latest build, once deploy will confirm sometime.

[murugan-ganesan]

@tapakund @dcasota we have deployed latest OVA build , we have not seen the node segmentation fault error. All the node module dependency its downloaded , node server started working fine.

Is there any other workflow it will impact?

[dcasota]

@murugan-ganesan many thanks for retesting it. Glad it worked so far.

@tapakund with regard to the pip3 ModuleNotFoundError: No module named 'pip'issue, this might be a python interpreter / pip-package mismatch caused by the python3.14 transition that Photon OS 5.0 was in the middle of around the time of the OVA build.
A sort of 'dependencies smoke run with parameters' as pre-flight check would be helpful.
Which option below is safety best practice?

• Either run python3 -m ensurepip --upgrade to rebuild pip against whichever python3 is now live, or
• tdnf reinstall python3-pip after the update, or
• pin the python3 and python3-pip versions explicitly in tdnf install ?

Regarding the vsi-proxy docker compose failure, one possible explanation is as follows:

• If the OVA build pipeline has upgraded docker compose and the newer version now resolves variables with a slightly altered precedence, variables that previously sourced from a shell export, an .env file, an OVF-property transfer, or an environment variable helper may now be resolving as empty.
• A build script invokes the docker socket via a python, go, or java client library, check that the client supports API ≥ 1.44. Older docker-py, docker-java, and dockerode versions silently return empty results against a v29 daemon. An "empty IP" landing in extra_hosts is exactly the symptom that pattern produces.

[tapakund]

Agree, as we updated python3 to 3.14 in Photon OS 5.0, post this change python3 generally looks at '/usr/lib/python3.14/site-packages/' for any imports by default.
On initial look, it looks like some pkg version mismatch causing this. If you could check the python3 version installed and reinstall python3-pip and give another try? Pls let us know if you still see the issue?

[tapakund]

@tapakund @dcasota we have deployed latest OVA build , we have not seen the node segmentation fault error. All the node module dependency its downloaded , node server started working fine.

Is there any other workflow it will impact?

We have fixed the issues in nodejs and i think its good now. Let me know if you find any issue.

[murugan-ganesan]

@tapakund thanks for each one support, so far, we are not found any issue we can be good to close now this open issue.

[dcasota]

Hi @murugan-ganesan -- thank you for the clear report and especially for retesting. Confirming on our side: the segfault was the upstream V8 Identical-Code-Folding crash (nodejs/node#47865), and the Photon fix '-fno-ipa-icf' landed in nodejs 24.14.1-2 and carries forward to the current available package, nodejs 24.16.0-1.ph5 (verified in a clean photon:5.0 container). That matches your 2026-04-30 verification that the latest OVA build no longer segfaults on npm install -g, and your 2026-05-08 note that you're good to close. One small heads-up for future fresh builds: make sure the pipeline runs 'tdnf update' so it pulls 24.14.1-2 or newer, since an un-updated 5.0 image can still ship the pre-fix 24.14.0 build. The pip3 'No module named pip' and vsi-proxy docker-compose empty-IP errors are unrelated -- best tracked separately if they persist. Since you've verified the node fix, shall we go ahead and close this one?