We fixed a bug in El Proxy related to the retry strategy for sending signed logs to Elasticsearch. Previously, after a document has been rejected from the Elasticsearch ingest pipeline, all non-signed logs were deleted during the retry phase including the mandatory “timestamp” field. Our solution now ensures that all mandatory fields remain intact during the retry strategy. Additionally, we enhanced the logging of El Proxy errors in the DLQ logs for easier debugging.
Upgrade Manager
We fixed a bug in the upgrade procedure related to fencing. The procedure now, whenever an update of pacemaker or corosync is present, ensures fencing is disabled to prevent possible issues when nodes are put in standby.
Furthermore, we fixed an issue related with the check of missing updates, which may have given an error in case a change of RedHat Release.
Updated packages
We updated the following packages:
elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup, elastic-blockchain-proxy-configurator to version 1.2.5-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