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

Kind e2e tests seem to flake during install with webhook error. #4791

Closed
vaikas opened this issue Jan 26, 2021 · 4 comments
Closed

Kind e2e tests seem to flake during install with webhook error. #4791

vaikas opened this issue Jan 26, 2021 · 4 comments
Labels
area/test-and-release Test infrastructure, tests or release kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@vaikas
Copy link
Contributor

vaikas commented Jan 26, 2021

Describe the bug

Last couple of days seen a few failures to install the eventing component (e2e tests are not failing, but install of eventing is):

Couple of examples are here:
https://github.com/knative/eventing/runs/1763499662?check_suite_focus=true
https://github.com/knative/eventing/runs/1763499632?check_suite_focus=true

customresourcedefinition.apiextensions.k8s.io/inmemorychannels.messaging.knative.dev created
deployment.apps/imc-controller created
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "config.webhook.eventing.knative.dev": Post https://eventing-webhook.knative-eventing.svc:443/config-validation?timeout=2s: dial tcp 10.96.251.146:443: connect: connection refused
deployment.apps/imc-dispatcher created
2021/01/25 17:03:45 error executing 'kubectl apply': exit status 1
Error: Process completed with exit code 1.

A clear and concise description of what the bug is.

Expected behavior
Tests to not flake.

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

@vaikas vaikas added the kind/bug Categorizes issue or PR as related to a bug. label Jan 26, 2021
@grantr
Copy link
Contributor

grantr commented Feb 1, 2021

@pierDipi does #4811 fix this? @vaikas thought it might.

@grantr grantr added area/test-and-release Test infrastructure, tests or release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 1, 2021
@pierDipi
Copy link
Member

pierDipi commented Feb 1, 2021

No, it doesn't, KinD E2E tests don't use chaosduck:

# Be KinD to these tests.
kubectl scale -n${SYSTEM_NAMESPACE} deployment/chaosduck --replicas=0

@vaikas
Copy link
Contributor Author

vaikas commented Feb 1, 2021

zomg, that's right I already asked that earlier :)

Thanks!

@vaikas
Copy link
Contributor Author

vaikas commented Feb 22, 2021

I went through the failed actions for the last 2 weeks, and I only see install failures related to the etcdserver failures:
#4975

I'm wondering if this got fixed by:
#4741

I'm closing, we can reopen if it comes back.

@vaikas vaikas closed this as completed Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test-and-release Test infrastructure, tests or release kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants