-
Notifications
You must be signed in to change notification settings - Fork 17
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
failed to register machine inventory: read elemental configuration: websocket: close 1006 (abnormal closure): unexpected EOF #176
Comments
Update: tested on a KVM single node kubernetes v1.23 K3s cluster, installed Rancher Manager v2.6.8, Operator version 0.5.0 commit 846c610. Client registration worked fine. The root cause of the failure is that the service account used by the operator has no secrets associated. |
When you have a fix available, I can also test it as I'm running into the same issue |
With Kubernetes 1.24, creation of ServiceAccounts no more triggers the creation of an associated Secret resource automatically: we need it for the ServiceAccount bound to the MachineRegistation resources. Explicitly create it in any case. Fixes #176 Signed-off-by: Francesco Giudici <[email protected]>
With Kubernetes 1.24, creation of ServiceAccounts no more triggers the creation of an associated Secret resource automatically: we need it for the ServiceAccount bound to the MachineRegistation resources. Explicitly create it in any case. Fixes #176 Signed-off-by: Francesco Giudici <[email protected]>
Confirmed fixed, thank you ! |
Elemental registration fails as indicated in $title.
Environment
Full log from
elemental-register --debug /run/initramfs/live
Full log from
elemental-operator
(copied fromk9s
)The text was updated successfully, but these errors were encountered: