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

[flakey] webhook.TestAdmissionInvalidResponseForResource #2432

Open
dprotaso opened this issue Feb 17, 2022 · 4 comments
Open

[flakey] webhook.TestAdmissionInvalidResponseForResource #2432

dprotaso opened this issue Feb 17, 2022 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@dprotaso
Copy link
Member

=== RUN   TestAdmissionInvalidResponseForResource
[2366](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2366)
    logger.go:130: 2022-02-15T16:23:56.397Z	INFO	webhook/webhook.go:200	Informers have been synced, unblocking admission webhooks.
[2367](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2367)
2022/02/15 16:23:56 http: TLS handshake error from 127.0.0.1:50900: EOF
[2368](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2368)
    logger.go:130: 2022-02-15T16:23:56.551Z	ERROR	webhook/webhook.go:150	failed to fetch secret	{"error": "secret \"webhook-certs\" not found"}
[2369](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2369)
2022/02/15 16:23:56 http: TLS handshake error from 127.0.0.1:50902: tls: no certificates configured
[2370](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2370)
    admission_integration_test.go:403: Failed to receive response Get "https://0.0.0.0:42363/booger": remote error: tls: unrecognized name
[2371](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2371)
    logger.go:130: 2022-02-15T16:23:56.552Z	INFO	webhook/webhook.go:242	Starting to fail readiness probes...
[2372](https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/2425/pull-knative-pkg-unit-tests/1493620921280237568#1:build-log.txt%3A2372)
--- FAIL: TestAdmissionInvalidResponseForResource (0.26s)
@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 19, 2022
@dprotaso
Copy link
Member Author

/lifecycle frozen

@dprotaso dprotaso reopened this Jun 21, 2022
@knative-prow knative-prow bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 21, 2022
@skonto
Copy link
Contributor

skonto commented Mar 8, 2024

@dprotaso is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants