Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1341964

Summary: Reports links should be removed
Product: Red Hat Enterprise Virtualization Manager Reporter: Lukas Svaty <lsvaty>
Component: rhevm-branding-rhevAssignee: Greg Sheremeta <gshereme>
Status: CLOSED ERRATA QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1.0CC: awels, bugs, gklein, lsurette, mgoldboi, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, thildred, ykaul
Target Milestone: ovirt-4.0.1   
Target Release: 4.0.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 21:14:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Svaty 2016-06-02 07:28:09 UTC 
Description of problem:
As reports are deprecated in 4.0 all the links mentioned should be removed from engine

Welcome page:
"Reports Portal" link
Reports and "Data Warehouse Guide [PDF]" 
  - change to "Data Warehouse Guide [PDF]"
  - change the the docs accordingly

ovirt page:
http://www.ovirt.org/documentation/how-to/reports/reports/
Comment 1 Moran Goldboim 2016-06-15 08:58:47 UTC 
changing milestone and put it as a blocker, this link should be removed as noted above to make sure we have a clear messaging.
Comment 2 Oved Ourfali 2016-06-15 09:32:20 UTC 
Seems like the welcome page was handled in Bug 1335199.
However, the docs might still have that, but they won't be part of the Beta anyway.

Greg - can you make sure that it is removed from the docs as well?

Changing the component accordingly.
Comment 5 Lukas Svaty 2016-07-26 09:57:41 UTC 
verified in ovirt-engine-4.0.2-0.2.rc1.el7ev.noarch
Comment 7 errata-xmlrpc 2016-08-23 21:14:07 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.

https://rhn.redhat.com/errata/RHBA-2016-1687.html