We fixed a bug that was preventing the first secure install of a cluster to success. Now the ClickHouse autosetup, which contained the spotted bug, has been fixed and updated.
Moreover we fixed two bugs related to Tenants having a name starting with numbers. In particular a bug that in this case caused the Satellite setup to fail when starting NATS Server, and a bug for which the default retention policy of InfluxDB databases (used by Telegraf) of such Tenants was not set correctly.
For NetEye 4.29 we updated the following packages:
neteye-setup to version 1.103.3-1
clickhouse-neteye-config to version 0.7.1-1
ntopng-neteye-config to version 1.10.2-1
icingaweb2-module-alyvix, icingaweb2-module-alyvix-autosetup to version 0.34.1-1
telegraf, telegraf-autosetup to version 1.23.4_neteye2.18.3-1
Fix Kibana sysconfig migration We resolved a bug that occurred during the migration of Kibana to a multi-instance setup. The issue prevented the proper copying of custom configurations from /neteye/shared/kibana/conf/sysconfig/kibana-user-customization. As a result, these customizations were missing from the Kibana instances Read More
Fix monitoring object creation during deployment We fixed a bug that caused a monitoring object to be lost if it was created while a Diretor deployment was in progress. List of updated packages To solve the issues mentioned above, the Read More
Fix for Tornado Webhook collector We have fixed an issue where large incoming requests to the Webhook Collector could cause the system to become unresponsive over time. List of updated packages To solve the aforementioned issues, the following packages have Read More
Fixes for Elastic Stack Improved wait for cluster status during updates / upgrades When restarting the Elasticsearch cluster during the NetEye update / upgrade procedure, is it possible let the restart procedure going even if the cluster has a "yellow" Read More
Fix for Previously, database updates would fail if the GLPI DRBD resource was active on a node other than the primary, due to an inability to locate the necessary database configuration within the DRBD-managed volume. This fix ensures that GLPI Read More
