ECK Operator Error - Cannot parse Elasticsearch error response body

I get this error with ECK 2.3.0 with elasticsearch 7.16.2

08-16-2022 12:05:48
Cannot parse Elasticsearch error response body
{"message":"Cannot parse Elasticsearch error response body","namespace":null}
invalid character 'o' in literal null (expecting 'u')

It's pretty consistent - any idea what this is due to and how this can be fixed/prevented?

I think you are hitting this issue Unhelpful error log on unmarshallable ES error response · Issue #5473 · elastic/cloud-on-k8s · GitHub

This can usually safely be ignored it was meant as an internal debugging tool but creates this unhelpful error message if the response is not the regular Elasticsearch error. We will fix it in a future release of the operator.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.