-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
None
-
False
-
-
False
-
-
-
Critical
Description of the problem:
Backstage pod init is failing due to
npm error path /opt/app-root/src/dynamic-plugins/dist/backstage-community-plugin-redhat-argocd/package.json npm error errno -2 npm error enoent Could not read package.json: Error: ENOENT: no such file
Versions
- csv: orchestrator-operator.v1.3.0-rc1
- catalogsource: quay.io/orchestrator/orchestrator-operator-catalog:v1.3.0-rc1
- helm chart: orchestrator-1.3.0-rc1
- rhdh-operator.v1.2.4 (shouldn't this be 1.3?)
How reproducible:
100%
Steps to reproduce:
1. Create orchestrator operator catalogsource from orchestrator-operator-catalog:v1.3.0-rc1
2. Deploy orchestrator via orchestrator operator (including all other components using orch operator)
Actual results:
oc logs -f backstage-backstage-6d8c7dc747-qzbtl -c install-dynamic-plugins ======= Installing dynamic plugin ./dynamic-plugins/dist/backstage-community-plugin-redhat-argocd ==> Grabbing package archive through `npm pack` Traceback (most recent call last): File "/opt/app-root/src/install-dynamic-plugins.py", line 304, in <module> main() File "/opt/app-root/src/install-dynamic-plugins.py", line 230, in main raise InstallException(f'Error while installing plugin { package } with \'npm pack\' : ' + completed.stderr.decode('utf-8')) InstallException: Error while installing plugin /opt/app-root/src/dynamic-plugins/dist/backstage-community-plugin-redhat-argocd with 'npm pack' : npm error code ENOENT npm error syscall open npm error path /opt/app-root/src/dynamic-plugins/dist/backstage-community-plugin-redhat-argocd/package.json npm error errno -2 npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/opt/app-root/src/dynamic-plugins/dist/backstage-community-plugin-redhat-argocd/package.json' npm error enoent This is related to npm not being able to find a file. npm error enoent npm error A complete log of this run can be found in: /opt/app-root/src/.npm/_logs/2024-10-17T14_41_26_364Z-debug-0.log
Expected results:{}
deployment succeeds
Expected results: