-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Data race during manager shutdown #2760
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
Comments
Maybe related to #2757 Are you able to update to latest v0.17 commit? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@ahmetb ^^ |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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-sigs/prow repository. |
I'd like to report a data race caught by
go test -race
during my end-to-end test suite (which usesenvtest
, but does not use Ginkgo) which ended up failing my test.The data race has occurred during the shutdown sequence. It seems during this time, one of the reconcilers was doing an API call, which ended up getting cancelled due to
ctx
cancellation I do as part of the tear down (to shut downenvtest
and theRunnable
s).I am not at all sure if it is related to
controller-runtime
, as the concurrent reader/writer goroutine stacks are pointing tonet/http
:But here it goes.
The text was updated successfully, but these errors were encountered: