Bug 894319
Summary: | Globally uncaught exception on navigating a resource after adding 'Resource Metric Graph' portlet to dashboard | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Sunil Kondkar <skondkar> | ||||||
Component: | UI | Assignee: | Mike Thompson <mithomps> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | urgent | ||||||||
Version: | JON 3.1.2 | CC: | jkremser, loleary, mithomps, myarboro, spinder | ||||||
Target Milestone: | CR03 | ||||||||
Target Release: | JON 3.1.2 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 895664 (view as bug list) | Environment: | |||||||
Last Closed: | 2013-09-11 11:04:35 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: | 852837 | ||||||||
Bug Blocks: | 895664 | ||||||||
Attachments: |
|
Description
Sunil Kondkar
2013-01-11 12:20:46 UTC
Created attachment 676836 [details]
Screenshot
Created attachment 676837 [details]
Error_details
I have characterized this a bit more... This bug occurs when you move from Dashboard to Inventory Detail view only if the dashboard contains Resource Metric Graphs that are configured (with metrics). And the workaround is to refresh the page. The application is stable until the above condition is met again. In effort to narrow down the offending commit from 3.1.1 to 3.1.2. I have found that the commit b9d4a5f introduces a new version of gflot (along with jquery, excanvas and sparklines). Consistent with the above behavior described, when you visit a gflot screen and then try to goto a screen with sparklines the erroneous behavior occurs. I was clued into this because the bug was stateful and not consistent. It takes a view of the Dashboard with a populated Resource Metric Graph to setup the condition for sparkline graphs to error out. If I take 3.1.2 CR1 and revert the above commit everything is fine (without the functionality that the commit fixes). Additional Info: This issue also exists in resource level dashboard and compatible group dashboard. ( Resource/Group->Summary->activity->Edit Mode->Add Resource Metric Graph portlet->select and save a resource and metric for the portlet and navigate to platform or any other resource in inventory.) This bug is related to bug 852837. per BZ triage, the fix for this will be targetted in JON 3.1.2 CR3 By backing out BZ 852837 with 2 commits b9d4a5f and 8000e71 this problem no longer occurs. BZ 852837 creates this problem so by backing it out this BZ never occurs. Just needs to be verified with QE that the problem no longer occurs. I've re-reverted the commits d069824b5 and 037e48a28 and pushed commit 8c1226a9b that solve both bugs. I was jQuery conflict (again). We should get rid of Gflot in the future. fixed in release/jon3.1.x http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=8c1226a9b time: Tue Jan 15 19:40:05 2013 +0100 commit: 8c1226a9b2bd3829f667b8cb1618ad9e6ce1ff37 author: Jirka Kremser - jkremser message: [BZ 894319 - Globally uncaught exception on navigating a resource after adding 'Resource Metric Graph' portlet to dashboard] Gflot now doesn't use its own version of jQuery. This bug was caused by the fact that Gflot lazily loads the jQuery to the page, so if user visited the dashboard before the page when Sparkline is used (resource summary tab), the exception was thrown. (cherry-picked from 5adfb817554307a6615e25cb6f952e1c1e9025bd, BZ 895664) Moving this to ON_QA since available for test in ER3. VERIFIED in JON 3.1.2 Verified on JON 3.1.2 CR3 build. Verified on main dashboard, resource level and compatible group level ..verified on Firefox 10, IE8 and IE9. The exception does not exist. |