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

Bug 1727520

Summary:	DWH admin portal dashboard queries use 4.2 views
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Shirly Radco <sradco>
Component:	ETL	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.5	CC:	bugs, dfediuck, lleistne
Target Milestone:	ovirt-4.3.5	Keywords:	TestOnly
Target Release:	4.3.5	Flags:	pm-rhel: ovirt-4.3+ dfediuck: ovirt-4.4? dfediuck: planning_ack? dfediuck: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-30 14:08:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1727521
Bug Blocks:

Description Shirly Radco 2019-07-07 06:18:52 UTC

Description of problem:
DWH admin portal dashboard queries use 4.2 views.
The queries should be updated to use the views based on the DWH version.

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


How reproducible:
100%

Steps to Reproduce:
1.Check admin portal queries and see the DWH views version are aligned with the engine and DWH version(4.3/4.4) 
2.
3.

Actual results:
All use 4.2 dwh views

Expected results:
Should use version aligned with the engine and DWH version(4.3/4.4) 

Additional info:

Comment 1 Sandro Bonazzola 2019-07-11 10:50:03 UTC

No new build is needed, for testing this you need latest ovirt-engine-4.3.5.4 for testing this.

Comment 2 Lucie Leistnerova 2019-07-12 10:52:27 UTC

I did not catch any v4_2 usage.

verified in ovirt-engine-dwh-4.3.5-1.el7ev.noarch

Comment 3 Sandro Bonazzola 2019-07-30 14:08:17 UTC

This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 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.