Bug 1618674 - Internal server error when I zoom out in Grafana dashboard
Summary: Internal server error when I zoom out in Grafana dashboard
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-monitoring-integration
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-17 09:41 UTC by Elena Bondarenko
Modified: 2019-05-08 18:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 16:23:44 UTC
Embargoed:


Attachments (Terms of Use)
Internal Server Error (110.28 KB, image/png)
2018-08-17 09:41 UTC, Elena Bondarenko
no flags Details

Description Elena Bondarenko 2018-08-17 09:41:05 UTC
Created attachment 1476591 [details]
Internal Server Error

Description of problem:

When I click Zoom out 19 times or more, I get Internal Server Error in the dashboard, as on the screenshot I attached here.


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

tendrl-ui-1.6.3-11.el7rhgs.noarch


How reproducible:

100%


Steps to Reproduce:

1. Log in to WA
2. Go to any dashboard
3. Click 'Zoom Out' 19 times or more

Actual results:

The panels on the dashboard show Internal Server Error


Expected results:

There's no Internal Server Error on the dashboard.

Comment 2 gowtham 2018-08-24 07:38:43 UTC
The date shows in grafana dashbaord in like oct 26, 1958. There is no historical data present in graphite for that date. So may be graphite unable to respond. I feel it is not a tendrl bug. It may be a grafana or graphite bug or it is expected behavior from grafana and graphite.

Comment 3 gowtham 2018-08-24 07:44:58 UTC
I checked in my machine, zoom out is actually changing the time rage. So the date which does not have a data is causing above issue.


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