We fixed a bug in the neteye update and neteye upgrade commands that was causing the NetEye default Logstash plugins to be installed from the Internet on passive cluster nodes. In particular this was causing the commands to fail in case these nodes did not have access to rubygems.org.
Updated packages
We updated the following packages:
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 version 8.11.3_neteye3.58.6-2
Damiano Chini
Author
Latest posts by Damiano Chini
31. 12. 2023
Development, DevOps, NetEye
Speeding up the NetEye CI Testing Phase