-
Bug
-
Resolution: Done
-
Blocker
-
1.4.0.Final
-
None
-
False
-
False
-
Undefined
-
-
-
2021 Week 13-15 (from Mar 29), 2021 Week 16-18 (from Apr 19), 2021 Week 19-21 (from May 10)
This is a major problem for Knative scenarios where the Broker forwards a message without the content-type header. Kogito services listening to these messages returns a 415 error:
{"level":"error","ts":"2021-04-15T04:51:14.471Z","logger":"inmemorychannel-dispatcher.knative.dev-eventing-pkg-reconciler-inmemorychannel-dispatcher.Reconciler","caller":"fanout/fanout_message_handler.go:283","msg":"Fanout had an error","knative.dev/pod":"imc-dispatcher-7bf7dd887d-4blp9","knative.dev/traceid":"7504b3c7-3fcf-4102-8f3e-ff0de2ae451a","knative.dev/key":"kogito-knative-bug/default-kne-trigger","error":"unable to complete request to http://broker-filter.knative-eventing.svc.cluster.local/triggers/kogito-knative-bug/trigger-notation/1b01e0cd-bae1-437a-8148-a14d59b67537: unexpected HTTP response, expected 2xx, got 415","stacktrace":"knative.dev/eventing/pkg/channel/fanout.(*FanoutMessageHandler).dispatch\n\t/opt/app-root/src/go/src/knative.dev/eventing/pkg/channel/fanout/fanout_message_handler.go:283\nknative.dev/eventing/pkg/channel/fanout.createMessageReceiverFunction.func1.1\n\t/opt/app-root/src/go/src/knative.dev/eventing/pkg/channel/fanout/fanout_message_handler.go:192"}
