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

in k3s master node, helper-pod could not execute successfully #11202

Open
RGaius opened this issue Nov 1, 2024 · 1 comment
Open

in k3s master node, helper-pod could not execute successfully #11202

RGaius opened this issue Nov 1, 2024 · 1 comment

Comments

@RGaius
Copy link

RGaius commented Nov 1, 2024

Environmental Info:
K3s Version:

k3s version v1.30.4+k3s1 (98262b5)
Node(s) CPU architecture, OS, and Version:

Linux 50 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

1 serves,2 agents
Describe the bug:

I am using ob-operator to deploy the oceanbase cluster, 50 is the master node, 51 and 52 are the work nodes.
the service on the current work node has been deployed normally, but the service deployment on the master node failed, and k3s indicates that the volume binding failed.

Steps To Reproduce:

  • Installed K3s:

Expected behavior:

Actual behavior:

Additional context / logs:

image
image
image
image
image

@brandond
Copy link
Member

brandond commented Nov 1, 2024

I don't know what you're demonstrating with the screenshots, as most of the captions aren't in English, and there's not much else to look at. I can't even tell what kind of nodes you have or what image this is running. However, the exec format error message usually indicates that the binary in the image is not the correct architecture for your nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

2 participants