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

fix: abort node watch on hostname change #10175

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

smira
Copy link
Member

@smira smira commented Jan 20, 2025

The method WaitForCacheSync might block for a long time, and looks like it can block forever if the nodename requested doesn't match the actual nodename.

Allow the wait to be aborted by running it in a goroutine, and notifying readiness of the watcher via the notifyCh.

Fixes #10163

The method `WaitForCacheSync` might block for a long time, and looks
like it can block forever if the nodename requested doesn't match the
actual nodename.

Allow the wait to be aborted by running it in a goroutine, and notifying
readiness of the watcher via the `notifyCh`.

Fixes siderolabs#10163

Signed-off-by: Andrey Smirnov <[email protected]>
@smira smira force-pushed the fix/k8s-node-status branch from 00c0d7e to 0b7fc7c Compare January 21, 2025 09:31
@smira
Copy link
Member Author

smira commented Jan 21, 2025

/m

@talos-bot talos-bot merged commit 0b7fc7c into siderolabs:main Jan 21, 2025
51 checks passed
@smira smira mentioned this pull request Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backported
Development

Successfully merging this pull request may close these issues.

Talos v1.9.2 nodes won't become ready, Kubernetes works
4 participants