Bug 1262828

Summary: missing headline in Trends Dashboard in case there is no datacenter
Product: Red Hat Enterprise Virtualization Manager Reporter: Karolína Hajná <khajna>
Component: ovirt-engine-reportsAssignee: Shirly Radco <sradco>
Status: CLOSED ERRATA QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: high    
Version: 3.6.0CC: gklein, lsurette, mgoldboi, pmatyas, pstehlik, rbalakri, Rhev-m-bugs, yeylon, ykaul, ylavi
Target Milestone: ovirt-3.6.2Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: rhevm-reports- Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 21:20:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Reports RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1286419    
Description Flags
Trends Dasboard Headline
Trends Dashboard none

Description Karolína Hajná 2015-09-14 12:46:31 UTC
Created attachment 1073232 [details]
Trends Dasboard Headline

Description of problem:
Headline in Trends Dashboard is missing or hidden. 

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

How reproducible:

Steps to Reproduce:
1. Go to reports portal
2. Open View -> Repository -> Trends Dashboard

Actual results:
Headline missing

Expected results:
Headline visible

Additional info:
Screenshot attached

Comment 3 Karolína Hajná 2015-12-28 09:19 UTC
Created attachment 1109992 [details]
Trends Dashboard

The headline is still now showing with rhevm-reports-

Comment 4 Shirly Radco 2015-12-28 11:03:13 UTC
The bug is only when there is only the default datacenter.

Comment 5 Shirly Radco 2016-01-03 10:15:42 UTC
Please check header for all 4 dashboards when there is a datacenter and when there is none.

Comment 6 Petr Matyáš 2016-01-21 12:46:52 UTC
Verified on 3.6.2-10

Comment 8 errata-xmlrpc 2016-03-09 21:20:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.