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

Bug 1133613

Summary: Change runTime to be set according to Engine DB date and time
Product: [Retired] oVirt Reporter: Shirly Radco <sradco>
Component: ovirt-engine-dwhAssignee: Shirly Radco <sradco>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: high    
Version: 3.5CC: ecohen, gklein, iheim, pstehlik, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: ovirt-3.5 rc2 ovirt-engine-dwh-3.5.0-0.9.fc19.noarch.rpm Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1133608 Environment:
Last Closed: 2014-10-17 12:29:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shirly Radco 2014-08-25 14:47:38 UTC
Description of problem:
If DWH and Engine are on seperate hosts we must check engine db and history db time is synced.
Otherwise the timestamp of the update date and delete date of the records will be incorect after deletion because they are taken from the current history db time.

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


How reproducible:


Steps to Reproduce:
1.Setup DWH and Engine on seperate hosts
2.Set different time for each host
3.Delete an entity and check the changes in the history db

Actual results:
Incurrect timstamp. Create Date is accurding to Engine DB time and Update/Delete Date are accurding to history db time.

Expected results:
Time of Engine and Histiry DBs should be synced.

Additional info:

Comment 1 Shirly Radco 2014-09-07 10:57:31 UTC
This is a semantic change.
We update the runTime to be updated from the engine db connection.
All timestamps are with timezones, so they were already updated correctly, but it makes more sence that the runTime for updateing the update and delete dates will be from the engine db connection.

Comment 2 Sandro Bonazzola 2014-10-17 12:29:08 UTC
oVirt 3.5 has been released and should include the fix for this issue.