Hide Forgot
Description of problem: configure_metrics playbook fails on patching externalIPs of the container as it is already set by previous run, therefore breaking idempotency of ansible Version-Release number of selected component (if applicable): ovirt-engine-metrics-1.1.4-0.0.master.20180408064245.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh 2. /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh 3. Actual results: TASK [oVirt.metrics/roles/oVirt.metrics-store-setup : Assign an IP Address to the Elasticsearch Service] ********************************************************************************************************** fatal: [10-37-138-124.rhev.lab.eng.brq.redhat.com]: FAILED! => {"changed": true, "cmd": "oc patch svc logging-es -p '{\"spec\":{\"externalIPs\":[\"10.37.138.124\"]}}'", "delta": "0:00:00.987452", "end": "2018-04-12 14:58:03.210222", "msg": "non-zero return code", "rc": 1, "start": "2018-04-12 14:58:02.222770", "stderr": "", "stderr_lines": [], "stdout": "service \"logging-es\" not patched", "stdout_lines": ["service \"logging-es\" not patched"]} Expected results: Check if externalIPs are set, if they are, do not patch
patch not included in ovirt-engine-metrics-1.1.4-1.el7ev.noarch please make sure ovirt-milestone is correct
apologies, updated wrong bug, verified in ovirt-engine-metrics-1.1.4-1.el7ev.noarch
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.