canonical / kubeflow-rocks

Rocks for Kubeflow components
Apache License 2.0
0 stars 11 forks source link

`kubeflow-dashboard` charm fails with `no such file or directory, open '//package.json'` when integrated with the rock #104

Closed DnPlas closed 4 months ago

DnPlas commented 5 months ago

Bug Description

When integrated with the charm, the following two images (the latest versions) fail with the same message:

To Reproduce

  1. Deploy CKF 1.8 or latest/edge
  2. Run juju refresh kubeflow-dashboard --resource oci-image=<image> to refresh the used image
  3. Check the container logs of the kubeflow-dashboard

Environment

Relevant Log Output

unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm - Start service "kubeflow-dashboard" (cannot start service: exited quickly with code 254)
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm ----- Logs from task 0 -----
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm 2024-06-19T13:56:54Z INFO Most recent service output:
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! code ENOENT
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! syscall open
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! path //package.json
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! errno -2
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! enoent ENOENT: no such file or directory, open '//package.json'
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! enoent This is related to npm not being able to find a file.
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! enoent
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR! A complete log of this run can be found in:
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     npm ERR!     /root/.npm/_logs/2024-06-19T13_56_53_931Z-debug-0.log
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm 2024-06-19T13:56:54Z ERROR cannot start service: exited quickly with code 254
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm -----
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm The above exception was the direct cause of the following exception:
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm Traceback (most recent call last):
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm   File "./src/charm.py", line 298, in <module>
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     main(KubeflowDashboardOperator)
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm   File "/var/lib/juju/agents/unit-kubeflow-dashboard-0/charm/venv/ops/main.py", line 439, in main
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm     framework.reemit()
unit-kubeflow-dashboard-0: 13:56:54 WARNING unit.kubeflow-dashboard/0.upgrade-charm   File "/var/lib/juju/agents/unit-kubeflow-dashboard-0/charm/venv/ops/framework.py", line 851, in reemit

Additional Context

No response

syncronize-issues-to-jira[bot] commented 5 months ago

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5889.

This message was autogenerated