-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
envtest - Failed to Watch error on every test run #904
Comments
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. |
I believe the issue here is that the k8sManager never receives on the channel from ctrl.SetupSignalHandler() to shutdown and like you mention the server and etcd are shutdown from underneath it. The manager needs to be shutdown cleanly first. |
Don't set verbose in 'make test' as envTest is really noisey in the integration tests. Also fixes an issue with the manager not being shut down cleanly at the end of integration tests which would result in error log output: kubernetes-sigs/controller-runtime#904
Don't set verbose in 'make test' as envTest is really noisey in the integration tests. Also fixes an issue with the manager not being shut down cleanly at the end of integration tests which would result in error log output: kubernetes-sigs/controller-runtime#904
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. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: 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. |
Was there any resolution for this issue? |
I'm using the
envtest
setup with ginkgo to test an operator.My test is setup like so:
My tests pass when I create my custom CR and check that operations were performed as expected, however, I always get this error message:
It looks like this is happening after the
etcd
and kubernetes API server have been shut down so I'm not sure what the problem is.Here's the full control plane output:
Using
sigs.k8s.io/controller-runtime v0.4.0
The text was updated successfully, but these errors were encountered: