[flaky] test/rekt: TestChannelDeadLetterSinkExtensions/Knative_Channel_-_DeadLetterSink_-_with_Extensions/channelSubscriberUnreachable/Assert/Receives_dls_extensions_when_subscriber_is_unreachable

[mgencur]

Describe the bug The test from title is failing randomly on OpenShift It is not clear from logs why the event was not delivered on dead letter sink. The sink seems to be ready and the channel has the dead letter sink attached in status.

Stacktrace:

event_info_store.go:177: Timeout waiting for at least 1 matches.
        Error: FAIL MATCHING: saw 0/1 matching events.
        - Store-
        Pod 'sink-jhargutc' in namespace 'serverless-tests'
        - Recent events -
        0 events seen, last 0 events (total events seen 296, events ignored 296):
        
        - Match errors -
        
        Collected events: 
        knative.dev/reconciler-test/pkg/eventshub.(*Store).AssertAtLeast
        	/go/src/knative.dev/eventing-istio/third_party/eventing/vendor/knative.dev/reconciler-test/pkg/eventshub/event_info_store.go:177
        knative.dev/reconciler-test/pkg/eventshub/assert.MatchAssertionBuilder.AtLeast.func1
        	/go/src/knative.dev/eventing-istio/third_party/eventing/vendor/knative.dev/reconciler-test/pkg/eventshub/assert/step.go:93
        knative.dev/reconciler-test/pkg/environment.(*MagicEnvironment).executeStep.func1
        	/go/src/knative.dev/eventing-istio/third_party/eventing/vendor/knative.dev/reconciler-test/pkg/environment/execution.go:67
        testing.tRunner
        	/usr/local/go/src/testing/testing.go:1446
        runtime.goexit
        	/usr/local/go/src/runtime/asm_amd64.s:1594
            --- FAIL: TestChannelDeadLetterSinkExtensions/Knative_Channel_-_DeadLetterSink_-_with_Extensions/channelSubscriberUnreachable/Assert/Receives_dls_extensions_when_subscriber_is_unreachable (240.00s)

Expected behavior The test is expected to pass.

To Reproduce Fails randomly. Hard to reproduce. The failure happened when Eventing was deployed with Istio.

Knative release version

Additional context Add any other context about the problem here such as proposed priority

[github-actions[bot]]

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.