Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1516632

Summary: Choice of Storage/Domain brings Uncaught Exception
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: Frontend.WebAdminAssignee: Daniel Erez <derez>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, pagranat, tjelinek
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-23 13:55:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
zip file contains ui.log , engine.log and screenshot none

Description Polina 2017-11-23 07:03:31 UTC
Created attachment 1358021 [details]
zip file contains ui.log , engine.log and screenshot

Description of problem:
Choice of Storage/Domain brings Uncaught Exception
Version-Release number of selected component (if applicable):


How reproducible:100%


Steps to Reproduce:
1.Open Storage tab/Storage Domains/. Choose some Domain 


Actual results:
brings error "Uncaught exception occurred. Please try reloading the page. Details: Encountered repeated errors resulting in an infinite loop. Make sure all users have access to the pages revealed by revealErrorPlace and revealUnauthorizedPlace. (Note that the default implementations call revealDefaultPlace)
Please have your administrator check the UI logs"

Expected results:
No error

Additional info:
logs and screenshot attached

Comment 1 Polina 2017-11-23 07:08:56 UTC
version - ovirt-engine-4.2.0-0.5.master.el7.noarch

Comment 2 Allon Mureinik 2017-11-23 13:31:53 UTC
Polina - can you please install the debug symbols package, rerun the scenario and attach the ui log again?
Thanks!

Also, where did this version come from? If this is the rhv-4.2.0-0.5 tag, it's pretty old (based on upstream master from about a month ago), and TBH, I wouldn't invest in researching it - I'd just take a newer build and make sure the bug doesn't reoccur.

Comment 3 Daniel Erez 2017-11-23 13:55:00 UTC
looks like a duplicate of 1513933

*** This bug has been marked as a duplicate of bug 1513933 ***