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.

Sign up for GitHub

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

Jump to bottom

🌱 Skip kube-vip-prepare for 1.31+ k8s since CAPI won't depend on super-admin.conf #18

Closed
wants to merge 2 commits into from
Closed

🌱 Skip kube-vip-prepare for 1.31+ k8s since CAPI won't depend on super-admin.conf #18

wants to merge 2 commits into from

Conversation

chrischdi
Copy link

@chrischdi
Copy link
Author

/test help

@team-cluster-api-prow
Copy link

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-31-1-32-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
  • /test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
  • /test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main
  • /test pull-cluster-api-provider-vsphere-test-main
  • /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-provider-vsphere-apidiff-main
  • /test pull-cluster-api-provider-vsphere-janitor-main

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-provider-vsphere-apidiff-main
  • pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
  • pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
  • pull-cluster-api-provider-vsphere-test-main
  • pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@chrischdi
Copy link
Author

/test pull-cluster-api-provider-vsphere-test-main
/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main

@chrischdi
Copy link
Author

/test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main

@chrischdi
Copy link
Author

Does not seem to work right away.

@chrischdi chrischdi closed this Aug 27, 2024
@chrischdi chrischdi mentioned this pull request Nov 18, 2024
Closed
@chrischdi chrischdi reopened this Nov 18, 2024
@chrischdi
Copy link
Author

/test help

@team-cluster-api-prow
Copy link

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-main
  • /test pull-cluster-api-provider-vsphere-e2e-govmomi-upgrade-1-31-1-32-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-ci-latest-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-conformance-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-main
  • /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main
  • /test pull-cluster-api-provider-vsphere-e2e-vcsim-govmomi-main
  • /test pull-cluster-api-provider-vsphere-e2e-vcsim-supervisor-main
  • /test pull-cluster-api-provider-vsphere-test-main
  • /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-provider-vsphere-apidiff-main
  • /test pull-cluster-api-provider-vsphere-janitor-main

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-provider-vsphere-apidiff-main
  • pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
  • pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
  • pull-cluster-api-provider-vsphere-test-main
  • pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@chrischdi
Copy link
Author

/test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main

@team-cluster-api-prow
Copy link

@chrischdi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main 3b77f26 link true /test pull-cluster-api-provider-vsphere-e2e-govmomi-blocking-main
pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main 3b77f26 link true /test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main
pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main 3b77f26 link true /test pull-cluster-api-provider-vsphere-e2e-supervisor-upgrade-1-31-1-32-main

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@chrischdi
Copy link
Author

From the cloud-init logs:

[2024-11-18 15:21:49] Running script /etc/pre-kubeadm-commands/20-k8s-install.sh
[2024-11-18 15:21:49] *************************************************
[2024-11-18 15:21:49] Detected Kubernetes v1.31.0 via kubectl version, nothing to do
[2024-11-18 15:21:49] Running script /etc/pre-kubeadm-commands/50-kube-vip-prepare.sh
[2024-11-18 15:21:50] W1118 15:21:50.355360    1293 initconfiguration.go:126] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/var/run/containerd/containerd.sock". Please update your configuration!
[2024-11-18 15:21:50] [init] Using Kubernetes version: v1.31.0
[2024-11-18 15:21:50] [preflight] Running pre-flight checks
[2024-11-18 15:21:50] [preflight] Pulling images required for setting up a Kubernetes cluster
[2024-11-18 15:21:50] [preflight] This might take a minute or two, depending on the speed of your internet connection
[2024-11-18 15:21:50] [preflight] You can also perform this action beforehand using 'kubeadm config images pull'
[2024-11-18 15:21:50] W1118 15:21:50.540440    1293 checks.go:846] detected that the sandbox image "registry.k8s.io/pause:3.9" of the container runtime is inconsistent with that used by kubeadm.It is recommended to use "registry.k8s.io/pause:3.10" as the CRI sandbox image.
[2024-11-18 15:21:50] [certs] Using certificateDir folder "/etc/kubernetes/pki"
[2024-11-18 15:21:50] [certs] Using existing ca certificate authority
[2024-11-18 15:21:50] [certs] Generating "apiserver" certificate and key
[2024-11-18 15:21:50] [certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local quick-start-eq-hqd95] and IPs [10.96.0.1 192.168.24.182 192.168.26.33]
[2024-11-18 15:21:50] [certs] Generating "apiserver-kubelet-client" certificate and key
[2024-11-18 15:21:50] [certs] Using existing front-proxy-ca certificate authority
[2024-11-18 15:21:51] [certs] Generating "front-proxy-client" certificate and key
[2024-11-18 15:21:51] [certs] Using existing etcd/ca certificate authority
[2024-11-18 15:21:51] [certs] Generating "etcd/server" certificate and key
[2024-11-18 15:21:51] [certs] etcd/server serving cert is signed for DNS names [localhost quick-start-eq-hqd95] and IPs [192.168.24.182 127.0.0.1 ::1]
[2024-11-18 15:21:51] [certs] Generating "etcd/peer" certificate and key
[2024-11-18 15:21:51] [certs] etcd/peer serving cert is signed for DNS names [localhost quick-start-eq-hqd95] and IPs [192.168.24.182 127.0.0.1 ::1]
[2024-11-18 15:21:51] [certs] Generating "etcd/healthcheck-client" certificate and key
[2024-11-18 15:21:51] [certs] Generating "apiserver-etcd-client" certificate and key
[2024-11-18 15:21:51] [certs] Using the existing "sa" key
[2024-11-18 15:21:51] [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[2024-11-18 15:21:52] [kubeconfig] Writing "admin.conf" kubeconfig file
[2024-11-18 15:21:52] [kubeconfig] Writing "super-admin.conf" kubeconfig file
[2024-11-18 15:21:53] [kubeconfig] Writing "kubelet.conf" kubeconfig file
[2024-11-18 15:21:53] [kubeconfig] Writing "controller-manager.conf" kubeconfig file
[2024-11-18 15:21:53] [kubeconfig] Writing "scheduler.conf" kubeconfig file
[2024-11-18 15:21:53] [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[2024-11-18 15:21:53] [control-plane] Using manifest folder "/etc/kubernetes/manifests"
[2024-11-18 15:21:53] [control-plane] Creating static Pod manifest for "kube-apiserver"
[2024-11-18 15:21:53] [control-plane] Creating static Pod manifest for "kube-controller-manager"
[2024-11-18 15:21:53] [control-plane] Creating static Pod manifest for "kube-scheduler"
[2024-11-18 15:21:53] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[2024-11-18 15:21:53] [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[2024-11-18 15:21:53] [kubelet-start] Starting the kubelet
[2024-11-18 15:21:54] [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests"
[2024-11-18 15:21:54] [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s
[2024-11-18 15:21:55] [kubelet-check] The kubelet is healthy after 1.00593382s
[2024-11-18 15:21:55] [api-check] Waiting for a healthy API server. This can take up to 4m0s
[2024-11-18 15:25:55] [api-check] The API server is not healthy after 4m0.000950491s
[2024-11-18 15:25:55] 
[2024-11-18 15:25:55] Unfortunately, an error has occurred:
[2024-11-18 15:25:55] 	context deadline exceeded
[2024-11-18 15:25:55] 
[2024-11-18 15:25:55] This error is likely caused by:
[2024-11-18 15:25:55] 	- The kubelet is not running
[2024-11-18 15:25:55] 	- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
[2024-11-18 15:25:55] 
[2024-11-18 15:25:55] If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
[2024-11-18 15:25:55] 	- 'systemctl status kubelet'
[2024-11-18 15:25:55] 	- 'journalctl -xeu kubelet'
[2024-11-18 15:25:55] 
[2024-11-18 15:25:55] Additionally, a control plane component may have crashed or exited when started by the container runtime.
[2024-11-18 15:25:55] To troubleshoot, list all containers using your preferred container runtimes CLI.
[2024-11-18 15:25:55] Here is one example how you may list all running Kubernetes containers by using crictl:
[2024-11-18 15:25:55] 	- 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
[2024-11-18 15:25:55] 	Once you have found the failing container, you can inspect its logs with:
[2024-11-18 15:25:55] 	- 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID'
[2024-11-18 15:25:55] error execution phase wait-control-plane: could not initialize a Kubernetes cluster
[2024-11-18 15:25:55] To see the stack trace of this error execute with --v=5 or higher
[2024-11-18 15:25:55] 2024-11-18 15:25:55,033 - cc_scripts_user.py[WARNING]: Failed to run module scripts_user (scripts in /var/lib/cloud/instance/scripts)
[2024-11-18 15:25:55] 2024-11-18 15:25:55,033 - util.py[WARNING]: Running module scripts_user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed

@chrischdi chrischdi closed this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@chrischdi @lubronzhan