Bug 1306689 - Exceptions in userportal when trying to open a console to a VM
Summary: Exceptions in userportal when trying to open a console to a VM
Keywords:
Status: CLOSED DUPLICATE of bug 1296458
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.UserPortal
Version: 3.6.2.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-11 15:18 UTC by Yevgeny Zaspitsky
Modified: 2016-02-12 09:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-12 08:36:26 UTC
oVirt Team: Virt
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yevgeny Zaspitsky 2016-02-11 15:18:45 UTC 
Description of problem:


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


How reproducible:
On RHEV-TLV 100$

Steps to Reproduce:
1. Try to open a console to a VM
2. After some time (looks like a timeout has been reached) pop-up window appears saying "Guest agent is not responsive".
At the same time the browser displays few (2-3) pink exception blocks (Uncaught exception occurred).
3. Click OK on "Guest agent is not responsive" message pop-up window. Several seconds later the console window opens.

Actual results:
Exceptions appear and a silly behavior.

Expected results:
Not ${actual_result}

Additional info:
Comment 2 Tomas Jelinek 2016-02-12 08:36:26 UTC 
The root cause of this is that after the console button is clicked the refresh interval is fastened. This causes race condition between getVms and getPools which causes NPEs. It has already been fixed for 3.6.3 (in that instance this issue happened after clicking run, but the root cause is the same).

Closing as duplicate

*** This bug has been marked as a duplicate of bug 1296458 ***
Note You need to log in before you can comment on or make changes to this bug.