-
Notifications
You must be signed in to change notification settings - Fork 600
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
Kind e2e tests sometimes fail with the webhook pod not becoming ready. #4496
Comments
Looking... Here's the step doing the wait:
|
https://github.com/knative/eventing/runs/1406746500?check_suite_focus=true
Yet the test failed with:
|
Does this look like: #3244 In knative-gcp, we will get crashed webhook, but maybe knative eventing automatically restart? |
@zhongduo I don't think so because the webhook becomes ready. |
But as you said, it is a different pod already. So it might as well be that we have some logic to detect the crash or unreadiness and restart the pod, which accidentally will solve the problem. |
This issue is stale because it has been open for 90 days with no |
This should've been fixed by: Let's reopen if it comes back. |
Describe the bug
Eventing webhook does not sometimes become ready, looks like maybe the specific one that the wait loop is waiting for gets replaced (maybe because of chaos duck?) by another pod that does become ready.
From one example here:
https://github.com/knative/eventing/pull/4492/checks?check_run_id=1381350649
Then when the artifacts are dumped, note a different webhook pod comes up:
Expected behavior
tests to not fail due to test setup failures.
To Reproduce
Look at some of these failing tests here:
https://github.com/knative/eventing/actions?query=workflow%3A%22KinD+e2e+tests%22
Knative release version
head
Additional context
Add any other context about the problem here such as proposed priority
The text was updated successfully, but these errors were encountered: