Bug 1717974 - Metrics Dashboard display a wrong value in 'Running VMs'
Summary: Metrics Dashboard display a wrong value in 'Running VMs'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.5-1
: 1.3.3
Assignee: Shirly Radco
QA Contact: Ivana Saranova
URL:
Whiteboard:
Depends On:
Blocks: 1721480
TreeView+ depends on / blocked
 
Reported: 2019-06-06 14:57 UTC by David Vaanunu
Modified: 2019-07-31 10:57 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-metrics-1.3.3
Clone Of:
Environment:
Last Closed: 2019-07-31 10:57:54 UTC
oVirt Team: Metrics
Embargoed:
sradco: ovirt-4.3?
sbonazzo: planning_ack?
sbonazzo: devel_ack?
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles logging pull 65 0 None closed Add ovirt.entity to ovirt collectd records 2020-09-06 14:03:50 UTC

Description David Vaanunu 2019-06-06 14:57:50 UTC 
RHV 4.3.4

While selecting in the Dashboard tab:
'Host Dashboard' or
'System Dashboard'
 

The value of 'Running VMs' is '0' although there are running VMs.

The VM query is wrong.
Comment 1 Shirly Radco 2019-06-10 08:11:03 UTC 
All vms related widgets in the dashboards should be verified for this bug.
Comment 2 Lucie Leistnerova 2019-07-16 12:59:30 UTC 
We don't have capacity now to verify metrics bugs. Moving to async 4.3.5-1.
Comment 3 Ivana Saranova 2019-07-22 14:22:52 UTC 
Steps:
1) Install metrics store and connect an engine with running VM to it according to the documentation
2) Check that all widgets in all dashboards containing information about the VMs are correct

Result:
All the widgets are showing correct information about the VM including number of running VMs, its name, cluster, host or engine.

Verified in:
ovirt-engine-metrics-1.3.3.2-1.el7ev.noarch
ovirt-engine-4.3.5.4-0.1.el7.noarch
Comment 4 Sandro Bonazzola 2019-07-31 10:57:54 UTC 
This bugzilla is included in oVirt 4.3.5 first async release, published on July 31th 2019.

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