Bug 1560922 - metrics store not being configured while scope are used
Summary: metrics store not being configured while scope are used
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.1.3.3
Hardware: All
OS: All
unspecified
high
Target Milestone: ovirt-4.2.2
: 1.1.3.4
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: 1475135
TreeView+ depends on / blocked
 
Reported: 2018-03-27 09:23 UTC by Lukas Svaty
Modified: 2018-04-18 12:26 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-metrics-1.1.3.4-1.el7ev
Clone Of:
Environment:
Last Closed: 2018-04-18 12:26:05 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89487 0 master MERGED Added the metrics_store machine to the --scope 2018-03-27 12:04:30 UTC

Description Lukas Svaty 2018-03-27 09:23:16 UTC
Description of problem:
If scope (engine or host) is used for configuring metrics playbook, metrics store is not being configured as it is not part of the scope, we need to add metrics store host group, to all scopes.

Version-Release number of selected component (if applicable):
ovirt-engine-metrics-1.1.3.3-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. On the fresh engine, run configure playbook with --scope-engine
2. Certificates are not being downloaded as metrics store playbooks are skipped

Comment 1 Lukas Svaty 2018-04-12 15:25:57 UTC
verified in ovirt-engine-metrics-1.1.4-0.0.master.20180408064245.el7.centos.noarch

Comment 2 Sandro Bonazzola 2018-04-18 12:26:05 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.


Note You need to log in before you can comment on or make changes to this bug.