Bug 1852752

Summary:	Fix chainsaw graphs
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Aviv Litman <alitman>
Component:	Grafana	Assignee:	Aviv Litman <alitman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.4.1	CC:	lleistne, pelauter, sradco
Target Milestone:	ovirt-4.4.2	Flags:	pm-rhel: ovirt-4.4+ pelauter: planning_ack+ sbonazzo: devel_ack+ lleistne: testing_ack+
Target Release:	4.4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-dwh-4.4.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-18 07:13:24 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:	1866734

Description Aviv Litman 2020-07-01 08:41:48 UTC

Description of problem:
We want to Fix chainsaw graphs 
We found 1 report that act like this.

Version-Release number of selected component (if applicable):
4.4.1

How reproducible:
100%

Steps to Reproduce:
1.go to oVirt Trend Dashboard
2.go to Hosts Trend Dashboard
3.look at Top 5 Busiest Ethernet Interface Tx and Rx Rates (over time) (BR2A) report
 
Actual results:
When you select the option for all the hosts, the graph behaves improperly (chainsaw)

Expected results:
The graph will behave normally without jumps

Additional info:

Comment 1 RHEL Program Management 2020-07-20 08:02:42 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Pavel Novotny 2020-08-28 22:21:32 UTC

Verified in
ovirt-engine-4.4.2.3-0.6.el8ev.noarch
ovirt-engine-dwh-4.4.2.1-1.el8ev.noarch

Comment 3 Sandro Bonazzola 2020-09-18 07:13:24 UTC

This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

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