Bug 1759102 - Error on VMs admin page on Chromium: "Cannot read property 'isEval' of undefined"
Summary: Error on VMs admin page on Chromium: "Cannot read property 'isEval' of undefi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.4.0
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On: 1752123
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-07 12:19 UTC by Marian Jankular
Modified: 2023-03-24 15:37 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1752123
Environment:
Last Closed: 2019-12-11 16:06:48 UTC
oVirt Team: UX
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)

Description Marian Jankular 2019-10-07 12:19:06 UTC
+++ This bug was initially created as a clone of Bug #1752123 +++

Description of problem:

On Chromium 76.0.3809.132, when I log into the oVirt engine and navigate to "Compute -> Virtual Machines", no VMs are visible and I get a JavaScript error:

> Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'isEval' of undefined
> Please have your administrator check the UI logs

The error doesn't appear in Firefox 69.0. 

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

Chromium: 76.0.3809.132
oVirt: 4.3.5.5-1.el7 (hosted engine)

How reproducible:

Very on my setup (not sure if it's setup-related).

Steps to Reproduce:
1. Log into web admin as an administrator
2. Navigate to Compute -> Virtual Machines

Actual results:

Error message described above. JS console shows an obfuscated stack trace:

> SEVERE: Uncaught exception (3x)
> com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'isEval' of undefined
> 	at Unknown.getOriginatingScriptUrl(<anonymous>)
> 	at Unknown.toDataURL(<anonymous>)
>
> jOe @ webadmin-0.js:20517
> s5f @ webadmin-0.js:19756
> r5f @ webadmin-0.js:15153
> A5f @ webadmin-0.js:13407
> m3m @ webadmin-0.js:18766
> Uen @ webadmin-0.js:15733
> bfn @ webadmin-0.js:20522
> Zu @ webadmin-0.js:17421
> wv @ webadmin-0.js:18936
> mv @ webadmin-0.js:16376
> Wu @ webadmin-0.js:15181
> Vu @ webadmin-0.js:19018
> (anonymous) @ webadmin-0.js:15563
> d @ webadmin-0.js:17255
> setTimeout (async)
> d @ webadmin-0.js:17255


Expected results:

VMs are shown and there's no error messages.

Additional info:

--- Additional comment from Sharon Gratch on 2019-09-16 10:44:01 UTC ---

This is not reproduced to me. Can you please attach engine and ui logs once it occurs? 
In addition, please try to clear the browser cache and see if it's reproduced.

--- Additional comment from Sharon Gratch on 2019-09-16 10:48:18 UTC ---

Does other views except the VMs (Clusters, Templates) work for you under the Compute menu?

--- Additional comment from Evert Nagel on 2019-09-16 14:08:18 UTC ---

Same issue observed, this was already happening with 4.2, remained after update to 4.3.
Log shows successfull login/test with Firefox at 15:43, then errors with Chrome. Both generate error about "SpiceVersion.txt".

Clearing cache, or disabling through DevTools does not make a difference.

Firefox works, other Compute menu items are fine.

Storage-Disks shows another error, not sure if related:
Mon Sep 16 15:55:25 GMT+200 2019 org.ovirt.engine.ui.uicompat.EnumTranslator
WARNING: Missing Enum resource 'V5'. Cannot find constant 'StorageFormatType___V5'; expecting a method name

--- Additional comment from Sharon Gratch on 2019-09-18 16:21:45 UTC ---

Since this issue was started at 4.2 then I guess it will be hard to reproduce. I suggest installing 4.3.6 on a clean environment and see if reproduced.

Comment 1 Michal Skrivanek 2019-10-08 07:16:10 UTC
there are few others, one is bug 1709773 fixed in current 4.3.z. Please upgrade.

Comment 2 Marian Jankular 2019-10-21 07:51:15 UTC
customer has upgraded to 4.3.6.7-0.1.el7 and still facing the problem

customer also confirmed that he is NOT experiencing the problem in firefox 69

Comment 3 Juan Orti 2019-12-11 15:19:30 UTC
Customer in case 02488340 has confirmed that the issue was caused by the browser plugin 'Privacy Badger'. It's working for them now.

Comment 4 Sharon Gratch 2019-12-11 15:33:45 UTC
(In reply to Juan Orti Alcaine from comment #3)
> Customer in case 02488340 has confirmed that the issue was caused by the
> browser plugin 'Privacy Badger'. It's working for them now.

Great, so I'm closing this bug and cloned Bug 1752123 as well.


Note You need to log in before you can comment on or make changes to this bug.