Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin fails when pod with PVC moves to a node with a different CPU architecture #1066

Open
isaacdorfman opened this issue Nov 26, 2024 · 0 comments

Comments

@isaacdorfman
Copy link

Describe the bug

Plugin fails when installed when pod is on one CPU architecture and recreated on another.

Error message:
logger=plugins.backend.start t=2024-11-26T11:08:26.069257688Z level=error msg="Could not start plugin backend" pluginId=yesoreyeram-infinity-datasource error="fork/exec /var/lib/grafana/plugins/yesoreyeram-infinity-datasource/gpx_infinity_linux_amd64: no such file or directory"

Note the gpx_infinity_linux_amd64 the plugin was installed when on an arm64 node so gpx_infinity_linux_amd64 doesn't exist.

Steps to reproduce

  1. Run the pod with a PVC on an amd64 node.
  2. Install the plugin
  3. Delete the pod and create another one mounting the same PVC on arm64 node.
@isaacdorfman isaacdorfman changed the title [Bug] Title Plugin fails when pod with PVC moves to a node with a different architecture Nov 26, 2024
@isaacdorfman isaacdorfman changed the title Plugin fails when pod with PVC moves to a node with a different architecture Plugin fails when pod with PVC moves to a node with a different CPU architecture Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant