Skip to content

[flakey] webhook.TestAdmissionInvalidResponseForResource #2432

Open

Description

@dprotaso
=== 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)

Activity

  1. github-actions commented on May 19, 2022

    @github-actions
    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.

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 19, 2022
  3. dprotaso commented on Jun 21, 2022

    @dprotaso
    MemberAuthor

    /lifecycle frozen

  4. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 21, 2022
  5. skonto commented on Mar 8, 2024

    @skonto
    Contributor

    @dprotaso is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions