Build Failure on OpenShift After Adding Kendo UI License

[Azhagu]

Verified active Kendo UI license in Telerik account. Downloaded telerik-license.txt and placed it in the project root.Installed @progress/kendo-licensing via npm install --save. Activated the license with npx kendo-ui-license activate.Confirmed all steps work locally.Encountering build error during OpenShift pipeline build after adding license.

Error: EACCES: permission denied, open '/opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/dist/index.mjs'
    at Object.openSync (fs.js:498:3)
    at Object.writeFileSync (fs.js:1529:35)
    at /opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:47542
    at Array.forEach (<anonymous>)
    at setRuntimeLicense (/opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:47301)
    at main (/opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:63927)
    at async /opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:64408 {
  errno: -13,
  syscall: 'open',
  code: 'EACCES',
  path: '/opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/dist/index.mjs'
}
[ERROR][Telerik and Kendo UI Licensing] Error while importing license.

[Martin Bechev]

Hello Azhagu,

Thank you for outlining the steps you have followed and noting that everything works locally but fails in your OpenShift pipeline with an EACCES permission.

Key Points & What’s Happening

• The error EACCES: permission denied, open '/opt/app-root/src/webapp/node_modules/@progress/kendo-licensing/dist/index.mjs' means the process running in your OpenShift build does not have write permissions to the node_modules/@progress/kendo-licensing/dist directory.
• This is common in containerized or CI/CD environments where the default user may not have the same permissions as your local development user.

How to Resolve

1. Confirm License Activation Step Placement

• The npx kendo-ui-license activate command must run after npm install and before your build step, and it must run as a user with write access to node_modules.
• In your pipeline, make sure the activation command is not running as a restricted user.

2. Explicitly Set Permissions (Pipeline Example)

You may need to add a step to update permissions before license activation. For example, in your pipeline YAML or Dockerfile, add:

# Grant write permissions to node_modules for the current user
chmod -R u+w node_modules
npx kendo-ui-license activate

Or, ensure the pipeline user has ownership of the directory:

chown -R $(whoami) node_modules
npx kendo-ui-license activate

Adjust the user as needed for your OpenShift setup.

3. Use Supported @progress/kendo-licensing Version

• Make sure you are using the latest version of @progress/kendo-licensing (1.6.0). Version 1.5.2 has a known issue with license activation.

Let us know how it goes.

Regards,

Martin Bechev
Progress Telerik