Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.
Describe the bug:
I use banzai-cloud/logging-operator 3.17.10 and banzai-cloud/logging-operator-logging 3.17.10 configured to send the logs to OpenSearch v2.5.0 with ElasticSearch plugin.
I would like to upgrade from v3.17.10 to v4.2.0.
When I try to upgrade with my current elasticsearch cluster output config I get an error that server is not Elasticsearch.
2023-04-17 16:03:59 +0000 [warn]: #0 suppressed same stacktrace
2023-04-17 16:03:59 +0000 [warn]: #0 [flow:logging:events:clusteroutput:logging:opensearch] failed to flush the buffer. retry_times=7 next_retry_time=2023-04-17 16:05:00 +0000 chunk="5f98a4f8e4d99797074acfbc8f0a54fc" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>\"log-opensearch1.myserver.com\", :port=>9200, :scheme=>\"https\", :user=>\"myuser\", :password=>\"obfuscated\"}, {:host=>\"log-opensearch1.myserver.com\", :port=>9200, :scheme=>\"https\", :user=>\"myuser\", :password=>\"obfuscated\"}): The client noticed that the server is not Elasticsearch and we do not support this unknown product.
When I change the output to opensearch and config to:
Describe the bug: I use banzai-cloud/logging-operator 3.17.10 and banzai-cloud/logging-operator-logging 3.17.10 configured to send the logs to OpenSearch v2.5.0 with ElasticSearch plugin. I would like to upgrade from v3.17.10 to v4.2.0.
When I try to upgrade with my current
elasticsearch
cluster output config I get an error that server is not Elasticsearch.When I change the output to
opensearch
and config to:I get an error of broken ruby gems in logging-operator-logging-fluentd-configcheck pod:
Expected behaviour: Fluentd config check passes and logs are sent to OpenSearch successfully.
Steps to reproduce the bug: Try to upgrade from version v3.17.10 to v4.2.0 with both configurations from above.
Environment details:
/kind bug