Bug 1138328

Summary: globally uncaught exception on storage metrics admin page
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: UIAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED CURRENTRELEASE QA Contact: Armine Hovsepyan <ahovsepy>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: jshaughn, mfoley
Target Milestone: ER03Keywords: Regression
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-11 14:05:01 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:
Attachments:
Description Flags
GUE
none
exception_gui.log none

Description Armine Hovsepyan 2014-09-04 13:53:03 UTC
Created attachment 934442 [details]
GUE

Description of problem:
globally uncaught exception on storage metrics admin page

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

How reproducible:
5 out of 10

Steps to Reproduce:
1. Uninventory platform with storage
2. As soon as platform and storage are auto-inventoried back -> Navigate to Administration -> Storage Nodes
3. Click on storage endpoint address link

Actual results:
globally uncaught exception on gui

Expected results:
metrics page should be loaded withot a GUE 


Additional info:
scree-nshot attached
no exception/error in server and/or agent logs

Comment 1 Armine Hovsepyan 2014-09-04 13:54:20 UTC
Created attachment 934443 [details]
exception_gui.log

Comment 2 Jay Shaughnessy 2014-09-08 13:56:31 UTC
I believe I fixed this issue as part of the work done for Bug 1071282 and Bug 1071291.  In release/jon3.3.x commit ee7abdce0d41b3797ea36e961067699b632858eb.

Setting to ON_QA as that commit made it into ER02.

Comment 3 Armine Hovsepyan 2014-09-08 15:16:45 UTC
The issue was found in ER02 while verifying above mentioned BZs
re-assigning back

Comment 5 Jay Shaughnessy 2014-09-12 18:38:35 UTC
Armine,  I still did not reproduce this (although I did not have the same multi-platfor env).  But I did find some things that may have contributed to the problem.  If by some chance you still see this, please check the server log for issues. If there is nothing there then it's going to be quite difficult to understand what the problem is...


master commit 58023b78baae102abdefa6d222a9a9d73dd69f0c
Author: Jay Shaughnessy <jshaughn>
Date:   Fri Sep 12 14:31:46 2014 -0400

 Although I was still unable to reproduce this bug I did find a couple of
 places where we needed to shore things up, that perhaps contributed.
 - fix getResourceIdFromStorageNode utility to throw the correct exceptions,
   this solves issues where caller catch definitions were not catching.
 - when uninventorying a Storage Node Resource we did not pro-actively unlink
   it from the StorageNode entity.  We did the unlink in the async work but
   that left the bad resource linked until async job ran or until
   it was re-linked to a newly imported SN resource.  Now unlinked up front
   (which is unfortunate as it adds another db query per batch).


release/jon3.3.x commit 6d39a26258d5bd2d5c6ec3a48a5d894344eb0682
Author: Jay Shaughnessy <jshaughn>
Date:   Fri Sep 12 14:31:46 2014 -0400

    (cherry picked from commit 58023b78baae102abdefa6d222a9a9d73dd69f0c)
    Signed-off-by: Jay Shaughnessy <jshaughn>

Comment 6 Simeon Pinder 2014-09-17 02:49:33 UTC
Moving to ON_QA as available for test with the following brew build:
https://brewweb.devel.redhat.com//buildinfo?buildID=385149

Comment 7 Armine Hovsepyan 2014-09-17 16:05:33 UTC
globally uncaught exception is not visible anymore in JON3.3 ER03 - moving to verified