Bug 1852752 - Fix chainsaw graphs
Summary: Fix chainsaw graphs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Grafana
Version: 4.4.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.4.2
: 4.4.2
Assignee: Aviv Litman
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks: 1866734
TreeView+ depends on / blocked
 
Reported: 2020-07-01 08:41 UTC by Aviv Litman
Modified: 2020-09-18 07:13 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-dwh-4.4.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-18 07:13:24 UTC
oVirt Team: Metrics
Embargoed:
pm-rhel: ovirt-4.4+
pelauter: planning_ack+
sbonazzo: devel_ack+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110332 0 master MERGED Fix bug in Hosts Trend Dashboard 2020-11-26 10:10:05 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.