-
Notifications
You must be signed in to change notification settings - Fork 592
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
e2e tests fail with pods not coming up. #4725
Comments
Failed again here:
|
Ok, so moar logs:
We're trying to fetch two different webhooks, one is found, other is not. It fails because the first is not found there:
And the st8fw pod is found there to be running:
From timestamps, I'd guess chaos killed them, but I can't seem to find the logs for chaos. Will look into it more. But furthermore will look at the waiting code to see if there's something there that we can look. I'd think we only care that the webhook is up, not that a particular webhook pod with a specific name is up. |
Yeah, so the step that does this is:
Which seems to turn into list calls where it is looking for specific pod names in the lists. |
chaos is disabled on KinD tests. eventing/.github/workflows/kind-e2e.yaml Lines 161 to 162 in d74dc25
Do we have more than one replica? |
I'm testing on KinD eventing-kafka-broker and failures I see are never related to the eventing webhook not coming up. |
@pierDipi hehe, that explains the no logs and disproves my theory :) |
Describe the bug
Here's one example
https://github.com/knative/eventing/pull/4724/checks?check_run_id=1687176531
Every now and then we observe a failure where the pods are supposedly not coming up even though they are. Working theory is that things get started, chaos duck kills something and somehow the list gets screwed because of this:
Yet, after collecting the system diagnostics we see this:
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
To Reproduce
Steps to reproduce the behavior.
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: