GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)
by Nadav Goldin
Hi,
Running OST basic-suite-master and logging to the GUI, appears a
warning pop-up window:
Uncaught exception occurred. Please try reloading the page. Details:
(TypeError) : a.i is undefined
Please have your administrator check the UI logs
ui.log:
2017-04-02 06:12:25,975-04 INFO
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-3) [] GWT symbolmaps are not installed, please install
them to de-obfuscate the UI stack traces
2017-04-02 06:12:25,980-04 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-3) [] Permutation name: E0637AA26393B2D56C4B42EFB5EA0C00
2017-04-02 06:12:25,980-04 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-3) [] Uncaught exception:
com.google.gwt.core.client.JavaScriptException: (TypeError) : a.i is
undefined
at Unknown.itp(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.Btp(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.pWo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.sWo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.JYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.MYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.jYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.mYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.PPe(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.E_(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.T_(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.onreadystatechange<(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.Bu(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.Eu(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.Du/<(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main)
at Unknown.anonymous(Unknown)
engine version: 4.2.0-0.0.master.20170402071029.git17ebf70.el7.centos
firefox: firefox-52.0-7.fc25.x86_64
Off hand, everything looks functional.
Thanks,
Nadav.
7 years, 7 months
[ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]
by Barak Korren
Test failed: test_initialize_engine
Link to suspected patches:
https://gerrit.ovirt.org/75054
Link to Job:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/
Link to all logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/artifa...
Error snippet from log:
<error>
2017-04-03 10:16:48 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:926 execute-output: ('/bin/systemctl', 'start',
'ovirt-engine.service') stderr:
Job for ovirt-engine.service failed because the control process exited
with error code. See "systemctl status ovirt-engine.service" and
"journalctl -xe" for details.
2017-04-03 10:16:48 DEBUG otopi.context context._executeMethod:142
method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132,
in _executeMethod
method['method']()
File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py",
line 57, in _closeup
state=True,
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state
service=name,
RuntimeError: Failed to start service 'ovirt-engine'
</error>
--
Barak Korren
bkorren(a)redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
7 years, 7 months
oVirt in the new programming-journal
by Arik Hadas
Hi everyone,
I would like to share a paper that has just been published in the new
programming-journal (that is called "The Art, Science, and Engineering of
Programming") named "Language Oriented Modularity: From Theory to Practice"
[1].
The evaluation of the proposed approach for language-oriented modularity
is done in part with oVirt (specifically, with the engine) and also
the difficulty/inability to reuse a DSAL that was designed for one
application in a different application is demonstrated with oVirt and
muCommander [2].
I hope you will find it interesting :)
[1] http://programming-journal.org/2017/1/10/
[2] https://github.com/mucommander
Regards.
Arik
7 years, 7 months
oVirt master UI now uses GWT 2.8
by Vojtech Szocs
Hello folks,
we're using the latest GWT version in master UI now [1].
We can start using Java 8 syntax in our frontend code. GWT 2.8 also brings
partial support for Java 8 standard library APIs, see "JDK emulation" at
[2] for details.
[1] https://gerrit.ovirt.org/#/q/topic:gwtupgrade
[2] http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1
Effectively, all Engine (Java Maven) modules [3] are now Java 8 source &
target compilant.
[3] except backend/manager/modules/extensions-api-root
With this upgrade, the GWT UI should be a bit faster - generated JavaScript
should take advantage of new web APIs (e.g. using ES6 Maps to implement
Java HashMap) as well as general performance improvements (e.g. using a
faster "long" emulation).
GWT 2.8 removes deRPC (direct-eval RPC) mechanism but that's OK because
we're already using the standard GWT RPC [4].
[4] https://gerrit.ovirt.org/#/c/65735/
There are no changes to existing build & development process:
- debugging via Java IDE (aka Classic Dev Mode) remains the default debug
method
- debugging via browser (aka Super Dev Mode) can be enabled via
DEV_BUILD_GWT_SUPER_DEV_MODE flag [5]
[5] example: $ make gwt-debug DEBUG_MODULE=webadmin
DEV_BUILD_GWT_SUPER_DEV_MODE=1
Note that in GWT 2.8 the Super Dev Mode is the new default debug method
(with Classic Dev Mode being deprecated).
There are still some post-upgrade tasks to do, we're tracking them on
Trello: https://trello.com/b/o26RrVLz/post-gwt-2-8-upgrade-tasks
If you encounter any issues related to GWT compilation or debugging, let me
know.
Regards,
Vojtech
7 years, 7 months
