Obfuscated UI exception message debugging
by Alexander Wels
Hi,
With the release of oVirt 3.6 the UI team added a handler for any uncaught
exceptions. This handlers shows a popup that basically says the following:
Uncaught exception occurred. Please try reloading the page. Details: [some
information]
With the some information giving some indication of what happened. Usually
that information is less than helpful. You can see the associated stack trace
in the browser console, but since all the code is obfuscated the stack trace
is usually pretty useless as well. I have been seeing a lot of bugs being
opened about the popup. In an effort to help everyone understand what is going
on and help us debug the root cause of the problem I created a wiki page [1]
that shows some steps to 'de-obfuscate' manually the stack trace and provide
hopefully some useful information.
Doing all of this labor intensive and not very intuitive, so in an effort to
automate the process, I have also created a patch that sends the obfuscated
stack trace to the engine and some code to automatically de-obfuscate the
stack trace and write it to a UI specific log [2]. Once that patch is merged
looking up UI exceptions should be as simple as looking in that log.
Hopefully the above will aid everyone in debugging any strange exceptions
generated by the UI.
Alexander
[1] http://www.ovirt.org/OVirt_Engine_Debug_Obfuscated_UI
[2] https://gerrit.ovirt.org/#/c/51558/
8 years, 10 months
[VDSM] [REVIEW] Introduce commands package to separate execCmd and AsyncProc from utils
by Nir Soffer
Hi all,
This patch moves execCmd and friends to new commands module, so code not using
these can be ported to Python 3. More work is needed to make execCmd compatible
with Python 3, and we don't want to delay the work on other modules
that do not depend
on it, but import utils.
Since this change touches all sub systems in vdsm, subsystems maintainers
should review and *verify* that it does not break anything.
Please review and verify:
https://gerrit.ovirt.org/51421
We are going to merge it on end of next week, so better check that it does not
break your code before that.
Thanks,
Nir
8 years, 10 months
com.google.gwt.event.shared.UmbrellaException
by Sandro Bonazzola
Hi,
not sure the following traceback is enough, but I've the system still
around and can provide more logs / info if needed.
Adding one host, in the dialog select use foreman / satellite, disable the
checkbox.
An exception is reported on the top of the admin interface and
in firefox console I see:
Wed Dec 23 08:23:59 GMT+100 2015
SEVERE: Uncaught exception: com.google.gwt.event.shared.UmbrellaException:
Exception caught: Exception caught: (TypeError)
__gwt$exception: <skipped>: zab(...) is null
at Unknown.ms(Unknown Source)
at Unknown.us(Unknown Source)
at Unknown.e3(Unknown Source)
at Unknown.h3(Unknown Source)
at Unknown.s2(Unknown Source)
at Unknown.Im(Unknown Source)
at Unknown.Sm(Unknown Source)
at Unknown.g$(Unknown Source)
at Unknown.Km(Unknown Source)
at Unknown.Vm(Unknown Source)
at Unknown.$Ve(Unknown Source)
at Unknown.$Xe(Unknown Source)
at Unknown.Yt(Unknown Source)
at Unknown.au(Unknown Source)
at Unknown._t/<(Unknown Source)
at Unknown.anonymous(Unknown Source)
Caused by: com.google.gwt.event.shared.UmbrellaException: Exception caught:
(TypeError)
__gwt$exception: <skipped>: zab(...) is null
at Unknown.ms(Unknown Source)
at Unknown.us(Unknown Source)
at Unknown.e3(Unknown Source)
at Unknown.h3(Unknown Source)
at Unknown.s2(Unknown Source)
at Unknown.Im(Unknown Source)
at Unknown.Sm(Unknown Source)
at Unknown.g2(Unknown Source)
at Unknown.N4e(Unknown Source)
at Unknown.B$(Unknown Source)
at Unknown.C2(Unknown Source)
at Unknown.s2(Unknown Source)
at Unknown.Im(Unknown Source)
at Unknown.Sm(Unknown Source)
at Unknown.g$(Unknown Source)
at Unknown.Km(Unknown Source)
at Unknown.Vm(Unknown Source)
at Unknown.$Ve(Unknown Source)
at Unknown.$Xe(Unknown Source)
at Unknown.Yt(Unknown Source)
at Unknown.au(Unknown Source)
at Unknown._t/<(Unknown Source)
at Unknown.anonymous(Unknown Source)
Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError)
__gwt$exception: <skipped>: zab(...) is null
at Unknown.s2u(Unknown Source)
at Unknown.RHr(Unknown Source)
at Unknown.hno(Unknown Source)
at Unknown.xno(Unknown Source)
at Unknown.n1u(Unknown Source)
at Unknown.p2u(Unknown Source)
at Unknown.RHr(Unknown Source)
at Unknown.hno(Unknown Source)
at Unknown.xno(Unknown Source)
at Unknown.o4u(Unknown Source)
at Unknown.s4u(Unknown Source)
at Unknown.Tuk(Unknown Source)
at Unknown.Zuk(Unknown Source)
at Unknown.f2(Unknown Source)
at Unknown.C2(Unknown Source)
at Unknown.s2(Unknown Source)
at Unknown.Im(Unknown Source)
at Unknown.Sm(Unknown Source)
at Unknown.g2(Unknown Source)
at Unknown.N4e(Unknown Source)
at Unknown.B$(Unknown Source)
at Unknown.C2(Unknown Source)
at Unknown.s2(Unknown Source)
at Unknown.Im(Unknown Source)
at Unknown.Sm(Unknown Source)
at Unknown.g$(Unknown Source)
at Unknown.Km(Unknown Source)
at Unknown.Vm(Unknown Source)
at Unknown.$Ve(Unknown Source)
at Unknown.$Xe(Unknown Source)
at Unknown.Yt(Unknown Source)
at Unknown.au(Unknown Source)
at Unknown._t/<(Unknown Source)
at Unknown.anonymous(Unknown Source)
com.google.gwt.event.shared.UmbrellaException
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 10 months
Failure running engine-setup on latest master
by Alexander Wels
Hi,
I am trying to run engine-setup on latest master and it is failing on the
database upgrade portion. The relevant part of the log is here. Can anyone
help me solve this?
psql:/home/awels/ovirt-**FILTERED**/share/ovirt-
**FILTERED**/dbscripts/common_sp.sql:1117: NOTICE: drop cascades to function
fn_db_get_async_tasks()
NOTICE: drop cascades to trigger delete_disk_image_dynamic_for_image on table
images
psql:/home/awels/ovirt-**FILTERED**/share/ovirt-
**FILTERED**/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql:57:
ERROR: integer out of range
FATAL: Cannot execute sql command: --file=/home/awels/ovirt-
**FILTERED**/share/ovirt-
**FILTERED**/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
2016-01-05 09:18:21 DEBUG otopi.context context._executeMethod:156 method
exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in
_executeMethod
method['method']()
File "/home/awels/ovirt-**FILTERED**/share/ovirt-
**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-
**FILTERED**/db/schema.py", line 291, in _misc
o**FILTERED**cons.EngineDBEnv.PGPASS_FILE
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 946, in
execute
command=args[0],
RuntimeError: Command '/home/awels/ovirt-**FILTERED**/share/ovirt-
**FILTERED**/dbscripts/schema.sh' failed to execute
Thanks,
Alexander
8 years, 10 months
FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo) - bad test? ci issue?
by Nir Soffer
Hi all,
We see this failure again in the ci - can someone from networking take a look?
18:16:52 ======================================================================
18:16:52 FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo)
18:16:52 ----------------------------------------------------------------------
18:16:52 Traceback (most recent call last):
18:16:52 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/ipwrapperTests.py",
line 130, in testEnablePromisc
18:16:52 "Could not enable promiscuous mode.")
18:16:52 AssertionError: Could not enable promiscuous mode.
18:16:52 -------------------- >> begin captured logging << --------------------
18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/brctl
show (cwd None)
18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link
add name vdsm-fS38VL type bridge (cwd None)
18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link
set dev vdsm-fS38VL up (cwd None)
18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link
set dev vdsm-fS38VL promisc on (cwd None)
18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
18:16:52 --------------------- >> end captured logging << ---------------------
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1838/con...
Thanks,
Nir
8 years, 10 months
4.0 GenericApiGWTService responses no longer being gzipped.
by Alexander Wels
Hi,
While I was the network traffic in my browser for an issue I was working on. I
noticed the response sizes being unusually large. When I compared it against a
similar sized 3.6 installation the response was huge. Checking the headers it
appears that the response no longer is gzipped before being send to the user.
Does anyone know of any changes to that recently? I am unsure of what exactly
gzipped the responses to begin with. I was assuming either a filter or some
jboss setting.
If anyone could shed some light on this it would be appreciated.
Thanks,
Alexander
8 years, 10 months
Jenkins server restarted
by Barak Korren
The oVirt Jenkins server seems to have gone into a particularly long
garbage collection process, so I just restarted it 10 minutes ago to
make it responsive again.
If you had jobs running at that time they will never finish, or finish
with failure, please restart them.
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
8 years, 10 months
