Bug 1402287

Summary: error message when there is not enough data
Product: Red Hat CloudForms Management Engine Reporter: Raul Mahiques <rmahique>
Component: UI - OPSAssignee: Federico Simoncelli <fsimonce>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: hkataria, jhardy, mpovolny, obarenbo, rmahique
Target Milestone: GA   
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 08:29:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot of the error shown none

Description Raul Mahiques 2016-12-07 07:56:18 UTC
Created attachment 1228922 [details]
screenshot of the error shown

Description of problem:
When i go to see the utilization of an OSE pod (or others) if i choose the previous day data (which is insufficient as it seems there is only one hour of data) i get an error message. (Attached)

Version-Release number of selected component (if applicable):
CFME Version:            5.6.1.2
cfme-gemset-5.6.1.2-1.el7cf.x86_64
cfme-appliance-5.6.1.2-1.el7cf.x86_64
cfme-5.6.1.2-1.el7cf.x86_64


How reproducible:
Install and configure CF, register one or multiple openshift providers with a running environment.

Steps to Reproduce:
1.Compute
2.Containers
3.Pod
4.Choose a pod that is running
5.Monitoring-> Utilization
6.Interval choose 'hourly', it will show some graphs, etc..
7.Now change the date to the previous day (in this case we only have data from yesterday night at around 11pm until now).
8.The error message attached will appear.

Actual results:
Error message.

Expected results:
Something nice like 'there is no data available for that period of time' or similar.

Additional info:

Comment 3 Federico Simoncelli 2016-12-12 09:40:55 UTC
We need the relevant evm.log and the production.log to debug this. Please attach.
Make sure they contain the error related to the error you're reporting.

Comment 6 Federico Simoncelli 2017-01-18 08:29:46 UTC
Closing this as we don't have any log and it seems not reproducible in 4.1.
Raul please reopen with more information in case you'll be able to reproduce.