+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1842260 +++ ====================================================================== Description of problem: When rying to send the metrics and logs to Elasticearch not on OCP, Can't set usehttps to false when also not using elasticsearch certificates (use_omelasticsearch_cert: false) Version-Release number of selected component (if applicable): 1.3.7 How reproducible: 100% Steps to Reproduce: 1. Set: rsyslog_elasticsearch_usehttps_metrics: off rsyslog_elasticsearch_usehttps_logs: off use_omelasticsearch_cert: false viaq_metrics_store: false elasticsearch_host: <The Elasticsearch host address> in the /etc/ovirt-engine-metrics/config.yml.d/config.yml file 2. Run the Rsyslog and Collectd configuration script ./configure_ovirt_machines_for_metrics.sh 3. Check the rsyslog elasticsearch conf file and see if usehttps is set to false. Actual results: Expected results: Additional info: (Originally by Shirly Radco)
Verified on: ovirt-engine-4.3.11-0.1.el7.noarch ovirt-engine-metrics-1.3.8-1.el7ev.noarch Steps: 1. installed elastic search in a fresh vm using the following repo/rpm https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rpm.html#rpm-repo 2. ran elasticsearch # echo "network.host: 0.0.0.0" >> /etc/elasticsearch/elasticsearch.yml # systemctl daemon-reload # systemctl start elasticsearch 3. on the engine, deployed rsyslog and collectd # vim /etc/ovirt-engine-metrics/config.yml.d/config.yml (set the ES fqdn) # /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh 4. checked if usehttps is set to false # grep usehttps /etc/rsyslog.d/30-elasticsearch.conf Results: usehttps is set to False
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Virtualization Engine security, bug fix 4.3.11), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4112