Hello, Kolla-Ansible is not supporting both opensearch and elasticsearch running at the same time - so if you’re using cloudkitty - it’s better to stick for Elasticsearch for now (CK does not support OpenSearch yet). I started working on the bug - will let you know in the bug report when a fix will be merged and images published. In the meantime you can try to uninstall the too-new elasticsearch gems using td-agent-gem uninstall in your running container image. Best regards, Michal
On 4 May 2023, at 14:33, wodel youchi <wodel.youchi@gmail.com> wrote:
Hi,
I'll try to open a bug for this.
I am using elasticsearch also with Cloudkitty : cloudkitty_storage_backend: "elasticsearch" instead of influxdb to get some HA. Will I still get the fluentd problem even if I migrate to Opensearch leaving Cloudkitty with elasticsearch???
Regards.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <x-msg://6/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Le jeu. 4 mai 2023 à 07:42, Michał Nasiadka <mnasiadka@gmail.com <mailto:mnasiadka@gmail.com>> a écrit :
Hello,
That probably is a Kolla bug - can you please raise a bug in launchpad.net <http://launchpad.net/>? The other alternative is to migrate to OpenSearch (we’ve back ported this functionality recently) - https://docs.openstack.org/kolla-ansible/yoga/reference/logging-and-monitori...
Best regards, Michal
On 3 May 2023, at 17:13, wodel youchi <wodel.youchi@gmail.com <mailto:wodel.youchi@gmail.com>> wrote:
Hi,
I have finished the update of my openstack platform with newer containers.
While verifying I noticed that fluentd container keeps restarting.
In the log file I am having this :
2023-05-03 16:07:59 +0100 [error]: #0 config error file="/etc/td-agent/td-agent.conf" error_class=Fluent::ConfigError error="Using Elasticsearch client 8.7.1 is not compatible for your Elasticsearch server. Please check your using elasticsearch gem version and Elasticsearch server." 2023-05-03 16:07:59 +0100 [error]: Worker 0 finished unexpectedly with status 2 2023-05-03 16:07:59 +0100 [info]: Received graceful stop
Those are the images I am using : (yogavenv) [deployer@rscdeployer ~]$ sudo docker images | grep -i elas 192.168.1.16:4000/openstack.kolla/centos-source-prometheus-elasticsearch-exporter <http://192.168.1.16:4000/openstack.kolla/centos-source-prometheus-elasticsearch-exporter> yoga030523 b48f63ed0072 12 hours ago 539MB 192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch <http://192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch> yoga030523 3558611b0cf4 12 hours ago 1.2GB 192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch-curator <http://192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch-curator> yoga030523 83a6b48339ea 12 hours ago 637MB
(yogavenv) [deployer@rscdeployer ~]$ sudo docker images | grep -i fluen 192.168.1.16:4000/openstack.kolla/centos-source-fluentd <http://192.168.1.16:4000/openstack.kolla/centos-source-fluentd> yoga030523 bf6596e139e2 12 hours ago 847MB
Any ideas?
Regards.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>