Bug 1717974
Summary: | Metrics Dashboard display a wrong value in 'Running VMs' | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine-metrics | Reporter: | David Vaanunu <dvaanunu> |
Component: | Generic | Assignee: | Shirly Radco <sradco> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivana Saranova <isaranov> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | bugs, lleistne |
Target Milestone: | ovirt-4.3.5-1 | Keywords: | ZStream |
Target Release: | 1.3.3 | Flags: | sradco:
ovirt-4.3?
sbonazzo: planning_ack? sbonazzo: devel_ack? lleistne: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-metrics-1.3.3 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Missing 'ovirt.entity' field in the metrics records.
Consequence:
VMs dashboard and Running VMs widget was broken
Fix:
Added the field to the metrics.
Result:
Dashboards will work as expected after they are reloaded again.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-31 10:57:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Metrics | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1721480 |
Description
David Vaanunu
2019-06-06 14:57:50 UTC
All vms related widgets in the dashboards should be verified for this bug. We don't have capacity now to verify metrics bugs. Moving to async 4.3.5-1. 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 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. |