This RFE applies to both WebAdmin & UserPortal. During GWT application compilation, symbol maps (mapping from Java identifier to obfuscated JavaScript identifier) are produced as *.symbolMap files, located in following directories: frontend/webadmin/modules/webadmin/target/generated-gwt/WEB-INF/deploy/webadmin/symbolMaps frontend/webadmin/modules/userportal-gwtp/target/generated-gwt/WEB-INF/deploy/userportal/symbolMaps These symbol maps can be very helpful when facing client-side errors manifested as obfuscated JavaScript stacktraces. Even though these symbol maps are not 100% accurate (see [1] for details), they are still a very good starting place. [1] https://code.google.com/p/google-web-toolkit/wiki/SourceMaps (see "Details" section describing symbol maps) Without using symbol maps, one has to compile GWT application in "draft" mode [2] and reproduce the problem on this "draft" application. Replacing "normal" GWT application with its "draft" version can be, however, problematic (especially in case the customer is the only one able to reproduce the error). [2] http://www.ovirt.org/DebugFrontend#GWT_Draft_Compile Symbol maps can be considered as meta-data bundled in WebAdmin & UserPortal rpm package.
As per discussion with Alon, we can introduce optional new packages like "ovirt-engine-webadmin-debug" and "ovirt-engine-webadmin-debug" containing GWT symbol maps.
after additional discussion with Alon: we will provide the symbol maps as part of the user-portal/web-admin RPMs. this is high-priority, as this will greatly assist in debugging GUI exceptions that currently contain obfuscated stacktrace information which is pretty useless.
Vojtech/Alon - I am not sure exactly who should be assigned to do this work; currently assigned to Vojtech, but if makes more sense for Alon to do this task - please re-assign accordingly. thanks.
Alon, is there anything else needed so these are delivered as part of all the builds, oVirt and RHEV?
(In reply to Michal Skrivanek from comment #4) > Alon, is there anything else needed so these are delivered as part of all > the builds, oVirt and RHEV? no, even if the rhev process will not auto distribute the debuginfo packages into channel, we can send these directly.
This is an automated message: This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.
this ovirt bug was fixed during 3.5.1 cycle and is included in the build, and therefore should be verified.
Verified in ovirt-engine-3.5.1-1.el6 GWT symbols are packaged in: ovirt-engine-webadmin-portal-debuginfo-3.5.1-1.el6.noarch ovirt-engine-userportal-debuginfo-3.5.1-1.el6.noarch and installed on system in directory: /usr/share/ovirt-engine/gwt-symbols/webadmin /usr/share/ovirt-engine/gwt-symbols/userportal
This is an automated message. oVirt 3.5.4 has been released on September 3rd 2015 and should include the fix for this BZ. Moving to closed current release.