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

Bug 1878496

Summary:	Add delete_date columns to uptime dashboard
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Aviv Litman <alitman>
Component:	Grafana	Assignee:	Aviv Litman <alitman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ivana Saranova <isaranov>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.1	CC:	lleistne
Target Milestone:	ovirt-4.4.3	Keywords:	ZStream
Target Release:	4.4.3	Flags:	pm-rhel: ovirt-4.4+ pm-rhel: planning_ack+ pm-rhel: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-dwh-4.4.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:39:50 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:
Bug Blocks:	1879377

Description Aviv Litman 2020-09-13 12:53:44 UTC

Description of problem:
We want to add 'delete_date' column to hosts and vms tables (3 tables).
so the host/vm delete date.

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

How reproducible:
100%

Steps to Reproduce:
1.go to oVirt Service Level Dashboards
2.go to Uptime Dashboard
3.look at Downtime by Host (BR7A), and Downtime by Virtual Machine (BR14A)

Actual results:
delete_date column is missing in 3 queries.

Expected results:
delete_date column is in the queries.

Comment 1 Ivana Saranova 2020-10-26 20:47:04 UTC

Steps:
1.go to oVirt Service Level Dashboards
2.go to Uptime Dashboard
3.look at Downtime by Host (BR7A), and Downtime by Virtual Machine (BR14A)

Results:
Delete date is in all the queries.

Verified in:
ovirt-engine-dwh-4.4.3.1-1.el8ev.noarch
ovirt-engine-4.4.3.8-0.1.el8ev.noarch

Comment 2 Sandro Bonazzola 2020-11-11 06:39:50 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

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