Bug 772462 - BR21 - Error when running reports due to not loading the dates
Summary: BR21 - Error when running reports due to not loading the dates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-reports
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.1
Assignee: Yaniv Lavi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-08 14:18 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-08-09 07:59:52 UTC
oVirt Team: ---


Attachments (Terms of Use)
ovirt-engine_serverLOG (249.68 KB, application/x-gzip)
2012-01-08 14:18 UTC, David Botzer
no flags Details

Description David Botzer 2012-01-08 14:18:13 UTC
Created attachment 551421 [details]
ovirt-engine_serverLOG

Description of problem:
After installing ETL before 2H had passed the dates are not loaded.
As a result of that BR21 gives Error

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

How reproducible:
only 2H since starting ETL

Steps to Reproduce:
1.Install ovirt-etl & start it
2.Open BR21
  
Actual results:
Report gets error

Expected results:
Should not load report until dates loaded, hence give error/alert that dates are empty

Additional info:
2012-01-08 14:50:14,236 INFO  [STDOUT] 2012-01-08 14:50:14,236  WARN DefaultRemoter,http-0.0.0.0-8080-3:67
 - Method execution failed: 
com.jaspersoft.jasperserver.api.JSExceptionWrapper: 
net.sf.jasperreports.engine.JRException: Error executing SQL statement for : Data_Centers
        at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java
:207)

Comment 1 Yaniv Lavi 2012-01-11 15:06:12 UTC
Fixed in commit:
http://gerrit.ovirt.org/993



Yaniv

Comment 2 Itamar Heim 2012-08-09 07:59:52 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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