-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
segfault validating cluster update after changing cluster name #3470
Comments
@erickt we need to improve validation, but you should not be able to change that field ;) |
Somehow the old cluster is coming back as nil, probably because he name has changed :) We need to fix the nil, and fix the validation. |
We're no longer going to segfault as of #3935. We do need validation that changing the name is not permitted. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/close |
I just tried to rename a cluster with kops with commit ea31478 and I got a segfault or nil pointer dereference. I did
kops edit cluster
and then changed the the metadata from:To:
Kops produced this backtrace:
The text was updated successfully, but these errors were encountered: