Bug 1043530

Summary: [REPORTS-SETUP] - upgrade from 3.2 failed to exportAdHoc - due to missing jiawsdatasource
Product: Red Hat Enterprise Virtualization Manager Reporter: Barak Dagan <bdagan>
Component: ovirt-engine-reportsAssignee: Itamar Heim <iheim>
Status: CLOSED ERRATA QA Contact: Barak Dagan <bdagan>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.3.0CC: acathrow, iheim, pstehlik, Rhev-m-bugs, sherold, srevivo, yeylon, ylavi
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: is28 - rhevm-reports-3.3.0-26.el6ev.noarch.rpm Doc Type: Bug Fix
Doc Text:
The reports database schema has been updated to be compatible with JasperServer 5.5, so now the import and export functionality operates correctly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 14:57:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1045855, 1046676    
Bug Blocks: 1049022    
Attachments:
Description Flags
reports setup log none

Description Barak Dagan 2013-12-16 15:00:18 UTC
Created attachment 837254 [details]
reports setup log

Description of problem:

During rhevm-reports installation, missing jiawsdatasource lead to failure of exporting adHoc part:

$ grep -A5 ERROR: ovirt-engine-reports-setup-2013_12_16_00_53_10.log
ERROR: relation "jiawsdatasource" does not exist
  Position: 4949
com.jaspersoft.jasperserver.api.JSExceptionWrapper: could not execute query; SQL [...]; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query

2013-12-15 14:07:22:EBUG::common_utils::493::root:: stderr =  -- JasperServer:  EhCacheImpl shutdown called.  This normal shutdown operation.
 -- JasperServer:  EhCacheImpl calling cleanerTimer.cancel().  This normal shutdown operation.
--
Caused by: org.postgresql.util.PSQLException: ERROR: relation "jiawsdatasource" does not exist
  Position: 4949
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
--
2013-12-15 14:07:22::ERROR::rhevm-reports-setup::614::root:: Exception caught, passing it along to main loop
2013-12-15 14:07:22::ERROR:ecorators::26::root:: Traceback (most recent call last):
  File "/usr/share/ovirt-engine-reports/decorators.py", line 21, in wrapped_f
    output = f()
  File "/usr/bin/rhevm-reports-setup", line 611, in exportAdHoc
    utils.execExternalCmd(cmd, True, "Failed while exporting ad hoc reports")
  File "/usr/share/ovirt-engine-reports/common_utils.py", line 497, in execExternalCmd
--
2013-12-15 14:07:22::ERROR::rhevm-reports-setup::1281::root:: Failed to complete the setup of the reports package!
2013-12-15 14:07:22:EBUG::rhevm-reports-setup::1282::root:: Traceback (most recent call last):
  File "/usr/bin/rhevm-reports-setup", line 1187, in main
    exportAdHoc()
  File "/usr/share/ovirt-engine-reports/decorators.py", line 27, in wrapped_f
    raise Exception(instance)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Lavi 2013-12-16 15:27:00 UTC
Jasper have broken the export scripts in JRS 5.5 GA by changing the db schema.
We need to save and use the old scripts from for the ad hoc export and use the new scripts for import. 



Yaniv

Comment 4 Barak Dagan 2014-01-16 16:31:22 UTC
verified on is32.2:

rhevm-reports-3.3.0-28.el6ev.noarch
rhevm-dwh-3.3.0-28.el6ev.noarch
jasperreports-server-pro-5.5.0-4.el6ev.noarch

Comment 6 errata-xmlrpc 2014-01-21 14:57:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0035.html