Bug 790043 - [ovirt-dwh] - ETL Is not working - Not collecting data to History DB
Summary: [ovirt-dwh] - ETL Is not working - Not collecting data to History DB
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-dwh
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Yaniv Lavi
QA Contact: David Botzer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-13 14:40 UTC by David Botzer
Modified: 2014-01-14 00:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 11:11:56 UTC
oVirt Team: ---

Attachments (Terms of Use)
server.log- (74.75 KB, application/x-gzip)
2012-02-13 14:40 UTC, David Botzer 		no flags Details
ETL_Log (123.61 KB, application/x-gzip)
2012-02-13 14:41 UTC, David Botzer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Botzer 2012-02-13 14:40:52 UTC 
Created attachment 561563 [details]
server.log-

Description of problem:
No data is gathered in ovirt_history db
As a result of working with ovirt-reports via GIT, and RPMs for engine,
The Reports is in a higher version than the engine, thus the ETL reports on a misconfiguration error, related to the versions

Version-Release number of selected component (if applicable):
ovirt-engine-3.0.0_0001-1.6.fc16.x86_64
reports 3.0 

How reproducible:
always

Steps to Reproduce:
1.Install ovirt-engine latest from RPMs
2.Install ovirt-dwh latest from GIT
  
Actual results:
Data is not collect in ovirt_history

Expected results:
should have one of the following:
1. packaging for ovirt-dwh/reports
2. GIT for engine


Additional info:
Comment 1 David Botzer 2012-02-13 14:41:17 UTC 
Created attachment 561564 [details]
ETL_Log
Comment 2 Itamar Heim 2012-02-14 03:37:21 UTC 
isn't this the expected behavior?
(i.e., solution should be for the devel environment)
Comment 3 Yaniv Lavi 2012-02-14 07:47:20 UTC 
We don't have packaging, so it's expected to have mismatches of version.
I also can not version correctly to make sure etl will not start as a result of this mismatche versions.


Yaniv
Note You need to log in before you can comment on or make changes to this bug.