Bug 977830 - [rhevm-reports_33] - Logs - Some log events are missing in jasperserver.log
Summary: [rhevm-reports_33] - Logs - Some log events are missing in jasperserver.log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.3.0
Assignee: Yaniv Lavi
QA Contact: Barak Dagan
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 12:45 UTC by David Botzer
Modified: 2016-02-10 19:22 UTC (History)
6 users (show)

Fixed In Version: rhevm-reports-3.3.0-6.el6ev.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 14:55:30 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0035 0 normal SHIPPED_LIVE rhevm-reports 3.3 bug fix and enhancement update 2014-01-21 19:53:30 UTC

Description David Botzer 2013-06-25 12:45:13 UTC 
Description of problem:
Logs - No logs in jasperserver.log at all

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

How reproducible:
always

Steps to Reproduce:
1.Install rhevm+dwh+reports
2.Examine jasperserver.log
  
Actual results:
No logs at all

Expected results:
Should show logs

Additional info:
Comment 1 Yaniv Lavi 2013-06-25 12:53:18 UTC 
Reopened case with jasper support number 00027147



Yaniv
Comment 2 Yaniv Lavi 2013-07-09 12:02:48 UTC 
Partly fixed in latest build. Still pending on Jasper on full fix.



Yaniv
Comment 4 David Botzer 2013-07-17 13:28:54 UTC 
3.3/is5
jasperreports-server-pro-5.2.0-1.el6ev.noarch
rhevm-reports-3.3.0-7.el6ev.noarch

When I open reports, and when I create new adhoc and generate report 
I dont see logs in jasperser.log
Comment 5 David Botzer 2013-07-18 07:11:43 UTC 
Fixed, 3.3/is5
jasperreports-server-pro-5.2.0-1.el6ev.noarch
rhevm-reports-3.3.0-7.el6ev.noarch

Logs are recorded correctly when error occurs,
Fixed, 3.3/is5
rhevm-reports-3.3.0-7.el6ev.noarch
Comment 6 Charlie 2013-11-28 00:48:47 UTC 
This bug is currently attached to errata RHEA-2013:15115. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 9 errata-xmlrpc 2014-01-21 14:55:30 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
Note You need to log in before you can comment on or make changes to this bug.