-
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
When using clusterctl init, it panics. #9128
Comments
This issue is currently awaiting triage. If CAPI contributors determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
Seems like a duplicate of #9101 - @chaunceyjiang could you check if the fix in #9107 works for you? |
This should be resolved on main once #9107 merges. Feel free to reopen if this looks like a separate issue on your side. Thanks for reporting this! |
/close |
@killianmuldoon: Closing this issue. In response to this:
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/test-infra repository. |
And just to be clear. This does not panic. It just prints a stacktrace. That's a huge difference :) |
Got it. Thanks~. @sbueringer @killianmuldoon |
What steps did you take and what happened?
What did you expect to happen?
There should not be any panic information.
Cluster API version
Kubernetes version
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: