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

Bug 1306689

Summary: Exceptions in userportal when trying to open a console to a VM
Product: [oVirt] ovirt-engine Reporter: Yevgeny Zaspitsky <yzaspits>
Component: Frontend.UserPortalAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.2.6CC: bugs, dpaz, michal.skrivanek, tjelinek, yliberma
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-12 08:36:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***