Fix Elasticsearch read-only indices check
We fixed an issue related to the 01002_elastic_indices_read_only_check.sh light health check, which checks if some indices are present in Elasticsearch in a read-only state.
The check may have wrongly recognized as in read-only also some indices where the read_only_allow_delete or read_only properties were set to false.
List of updated packages
To solve the issue, the following packages have been updated
elastic-agent,elastic-agent-autosetup,elastic-agent-neteye-config,elastic-stack-configurator,elasticsearch,elasticsearch-autosetup,elasticsearch-neteye-config,elasticsearch-xpack-license,filebeat,filebeat-autosetup,filebeat-neteye-config,kibana,kibana-autosetup,kibana-neteye-config,logstash,logstash-autosetup,logstash-neteye-config,logstash-neteye-config-autosetupto version8.17.3_neteye3.74.3-1
MariaDB upgrade prerequisite check
We added a prerequisite check for the upgrade to NetEye 4.41, which ensures old MariaDB upgrades were correctly performed.
List of updated packages
To solve the issue, the following packages have been updated:
mariadb-neteye-config,mariadb-neteye-config-autosetupto version1.6.4-1
Command Orchestrator remote commands failure
We fixed a bug that prevented the Command Orchestrator (CMDO) remote commands to be executed successfully.
List of updated packages
To solve the issue, the following packages have been updated:
icingaweb2-module-cmdorchestratorandicingaweb2-module-cmdorchestrator–autosetupto version0.20.1-1icingaweb2-module-neteyeandicingaweb2-module-neteye-autosetupto version1.64.3-1
Davide Sbetti
Hi! I'm Davide and I'm a Software Developer with the R&D Team in the "IT System & Service Management Solutions" group here at Würth IT Italy. IT has been a passion for me ever since I was a child, and so the direction of my studies was...never in any doubt! Lately, my interests have focused in particular on data science techniques and the training of machine learning models.
Author
Latest posts by Davide Sbetti
30. 06. 2026
AI, Kubernetes
Load-balancing Requests to LLMs in Kubernetes: A KV-cache Approach with llm-d!