Red Hat Bugzilla – Bug 1020340
[PENDING JASPER] Report page not loading
Last modified: 2016-06-26 19:50:46 EDT
Created attachment 813332 [details]
Screenshot of the reports page with popup
Description of problem:
When accessing the 'dashboard' tab a popup shows up with html code in it, and the reports page shows four 'loading' gifs all the time.
Version-Release number of selected component (if applicable):
Install rpms, run engine-setup, rhevm-dwh-setup, rhevm-reports-setup, add iscsi domain, create a few machines and hit the dashboard tab.
Steps to Reproduce:
2.Run setup for engine, dwh and reports
3.Create a few machines
4.Go to dashboard tab
A popup with html code and page shows 4 loading gifs (see attached screenshot)
Reports page correctly loading.
sounds similar to bug 1017163, which was closed due to inability to reproduce. David - are you able to reproduce it consistently?
Yes, I am.
Reproduced again, reinstalled is19, set up a DC with one host and one vm, then ran dwh-setup and after reports-setup, and after that (engine gets restarted twice) went to the created dc 'dashboard' tab and got the same result.
(In reply to David Caro from comment #2)
> Yes, I am.
> Reproduced again, reinstalled is19, set up a DC with one host and one vm,
> then ran dwh-setup and after reports-setup, and after that (engine gets
> restarted twice) went to the created dc 'dashboard' tab and got the same
many thanks, David. Can you please attach logs?
@Oved: Any chance that you can pick it up from here?
[again, it seems extremely similar to bug 1017163, which you have already investigated]
Please attach logCollection on the rhevm server (it collects also jasperServer logs)
Opened case number 00040416.
Adding additional info:
1) The report dashboard, doesn't load indeed using FF
2) The report dashboard, do start loading after a while using chrome, and then jumno pop up containing : "<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">". After confirm, the page stuck with the "loading" gifs.
*** Bug 1017863 has been marked as a duplicate of this bug. ***
Verification failed on IS21:
# rpm -qa | egrep 'report|dwh'
Same results. NO dsahboard in FF, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> in chrome
*** This bug has been marked as a duplicate of bug 1029023 ***
*** Bug 1029023 has been marked as a duplicate of this bug. ***
verification failed on is24.2, rhevm-reports-3.3.0-22.el6ev.noarch:
The following message recived:
"Internal server error occurred. Please contact your system administrator.
Details: Could not execute JDBC batch update; SQL [insert into JIRole (rolename, tenantId, externallyDefined, id) values (?, ?, ?, ?)]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update"
(In reply to Barak Dagan from comment #15)
> verification failed on is24.2, rhevm-reports-3.3.0-22.el6ev.noarch:
> The following message recived:
> "Internal server error occurred. Please contact your system administrator.
> Details: Could not execute JDBC batch update; SQL [insert into JIRole
> (rolename, tenantId, externallyDefined, id) values (?, ?, ?, ?)]; constraint
> [null]; nested exception is
> org.hibernate.exception.ConstraintViolationException: Could not execute JDBC
> batch update"
Barak, are you testing with upgraded engine, cause this error looks like the error we has with the api issue pre IS24.1?
Juan any idea?
There is no upgraded engine !!!
As can be seen from Version table changes: http://bob.eng.lab.tlv.redhat.com/builds/is24.2/is24.2_version_info.html
(In reply to Barak Dagan from comment #17)
> There is no upgraded engine !!!
> As can be seen from Version table changes:
As I said above "pre IS24.1".
this was the latest version I got from CI
should be in for is25
Verified on IS25.
got all 3 dashboard (general, dc, cluster)
This bug is currently attached to errata RHSA-2013:15137 . 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:
Thanks in advance.
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.