-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unable to provision a node capi-kubeadm-control-plane-controller #2613
Labels
area/control-plane
Issues or PRs related to control-plane lifecycle management
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
Comments
|
We hit this problem also in the Metal3 CI. We have exactly the same trace in the CACPK webhook server. |
I guess the problem is coming from here: |
The actual issue is probably that we do not have a ClusterConfiguration in the CR |
We probably should handle the nil pointer better, though |
/assign |
k8s-ci-robot
added
the
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
label
Mar 10, 2020
vincepri
added
area/control-plane
Issues or PRs related to control-plane lifecycle management
area/clusterctl
Issues or PRs related to clusterctl
and removed
area/clusterctl
Issues or PRs related to clusterctl
labels
Mar 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/control-plane
Issues or PRs related to control-plane lifecycle management
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
What steps did you take and what happened:
Deploy a control plane node
What did you expect to happen:
A control plane node be deployed successfully.
Anything else you would like to add:
[Edit]
Only the following issue is to be fixed.
Provisioning fails due to
runtime error: invalid memory address or nil pointer dereference
Environment:
/kind bug
The text was updated successfully, but these errors were encountered: