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

Creating CAPA cluster fails with "control-plane-endpoint" registration #332

Closed
alexander-demicev opened this issue May 21, 2024 · 1 comment
Labels
kind/bug Something isn't working lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@alexander-demicev
Copy link
Member

Creating CAPA cluster fails with "control-plane-endpoint" registration, machines fail to join initial CP with the following error:

May 20 21:33:42 ip-10-0-247-124.us-west-1.compute.internal systemd[1]: rke2-server.service: Failed with result 'exit-code'.
May 20 21:33:42 ip-10-0-247-124.us-west-1.compute.internal systemd[1]: Failed to start Rancher Kubernetes Engine v2 (server).
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal systemd[1]: rke2-server.service: Scheduled restart job, restart counter is at 25.
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal systemd[1]: Stopped Rancher Kubernetes Engine v2 (server).
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal systemd[1]: Starting Rancher Kubernetes Engine v2 (server)...
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal sh[2682]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal sh[2683]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal rke2[2686]: time="2024-05-20T21:33:47Z" level=warning msg="not running in CIS mode"
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal rke2[2686]: time="2024-05-20T21:33:47Z" level=info msg="Applying Pod Security Admission Configuration"
May 20 21:33:47 ip-10-0-247-124.us-west-1.compute.internal rke2[2686]: time="2024-05-20T21:33:47Z" level=info msg="Starting rke2 v1.26.0+rke2r1 (22513ef9e5b17b9910558bfe2091253a00718780)"
May 20 21:34:07 ip-10-0-247-124.us-west-1.compute.internal rke2[2686]: time="2024-05-20T21:34:07Z" level=fatal msg="starting kubernetes: preparing server: failed to get CA certs: Get \"https://xxx.elb.us-west-1.amazonaws.com:9345/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
@alexander-demicev alexander-demicev added the kind/bug Something isn't working label May 21, 2024
Copy link

This issue is stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Development

No branches or pull requests

1 participant