- Devel - oVirt List Archives

[ OST Failure Report ] [ oVirt master ] [ 3/4/2017 ] [test_intialize_engine]
by Barak Korren 03 Apr '17

03 Apr '17

Link to suspected patches: https://gerrit.ovirt.org/#/c/73688/ Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/artif… Error snippet from log: <error> [ INFO ] Starting engine service [ ERROR ] Failed to execute stage 'Closing up': Failed to start service 'ovirt-engine' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20170403084130-sfzp94.log </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/Test failed: [ TEST NAME ]

2 1

GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)
by Nadav Goldin 03 Apr '17

03 Apr '17

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.

4 8

[ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]
by Barak Korren 03 Apr '17

03 Apr '17

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/artifact… 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/

2 1

oVirt in the new programming-journal
by Arik Hadas 03 Apr '17

03 Apr '17

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

2 1

oVirt master UI now uses GWT 2.8
by Vojtech Szocs 02 Apr '17

02 Apr '17

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

2 1

Re: [ovirt-devel] Interest in contributing to oVirt
by Konrad Djimeli 31 Mar '17

31 Mar '17

Hello Yaniv, Thanks very much for the response. I am currently trying to develop a proposal for this project but I have not yet been able to successfully setup oVirt. I just realized I could not install the oVirt-engine an Ubuntu 14, so I am currently trying to download and install Fedora 23, where I intend to setup the oVirt-engine. I would then use another machine with Ubuntu for the host. Please with respect to this project I would like to know if I am also required compile and install the source code for oVirt-engine or do I only need to build and install ovirt4cli. Thanks Konrad On 17 March 2017 at 20:26, Yaniv Kaul <ykaul(a)redhat.com> wrote: > Hi Konrad, > > I'm very happy to hear that and wish you good luck with the project. > > I think it'd be best if you can begin with familiarizing yourself with > oVirt. > If you have few computers around, it should be fairly easy to set it up. If > you have a single computer, you can set up Lago[1] and ovirt-system-test[2] > to bring up an environment as well. > > The (very basic) code for ovirt4cli is available on my github[3] - I have > just created a very basic framework as a proof of concept - feel free to > fork and modify it. Specifically, I think we should re-work it to share more > code with our Ansible code[4]. > > Let me know if there's anything I can help you with in the project! > Y. > > [1] http://lago.readthedocs.io/en/stable/ > [2] http://ovirt-system-tests.readthedocs.io/en/latest/ > [3] https://github.com/mykaul/ovirt4cli > [4] > https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/ovir… > > > On Fri, Mar 17, 2017 at 9:06 AM, Konrad Djimeli <djkonro35(a)gmail.com> wrote: >> >> Hello, >> >> My name is Konrad Djimeli a third year Computer Science Student at the >> University of Buea, Cameroon. I am interested in contributing to oVirt >> and I would like to work on the Google Summer of Code project >> "ovirt4cli". I am very comfortable working with Python and I have >> experience working with web services like REST. >> >> Please I would appreciate any suggestion on how to get started and to >> better familiarize myself with the project. >> >> >> Thanks >> Konrad >> http://djimeli.me/ > >

2 2

[ANN] oVirt 4.1.1 Async release candidate
by Sandro Bonazzola 30 Mar '17

30 Mar '17

Hi, following oVirt 4.1.1 GA the oVirt team identified some bugs worth to be addressed out of the usual release cycle. For this reason an async release including these fixes is under preparation. An update to the following packages have been pushed to the pre-release repository for testing. - ovirt-engine-4.1.1.7 - vdsm-4.19.10.1 - ovirt-release41-4.1.1.1_rc1 - ovirt-web-ui-0.1.2-4 - cockpit-ovirt-0.10.7-0.0.16 In order to test it, you'll need pre-release repository enabled: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41-pre.rpm An update to release notes including bugs related to above packages and updates applied in bugzilla documentation texts has been pushed to https://github.com/oVirt/ovirt-site/pull/888 for review. On behalf of the oVirt team, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[OST failure report] vdsmfake doesn't produce artifacts
by Pavel Zhukov 30 Mar '17

30 Mar '17

Hello, Vdsmfake doesn't build any installable artifacts and deploy-to* job fails because of this. Example: See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/14413> Can someone take a look please? -- Pavel Zhukov Software Engineer

2 1

Writing SQL queries in DAO code
by Yevgeny Zaspitsky 30 Mar '17

30 Mar '17

Hi All, Recently I had a task of performance improvement in one of our network related flows and had some hard time following our DAL code and one of the outcomes of the task was defining a couple of new quite simple, but neat queries. When I came to coding those new queries I remembered how hard was following the existing DAL code, I decided to make my own new methods clearer. So I created [1] and [2] patches. Everything is quite standard there beside the fact that they do not use any stored procedure, but use SQL directly, IMHO by that they save time that I spent in trying to follow what a DAO method does. Looking into the method code you get the understanding of what this method is all about: - no looking for a stored procedure name that is buried in the DAO class hierarchy - no looking for the SP definition So I'd like to propose moving towards this approach in general in all cases when nothing beyond a simple SQL is needed (no stored procedure programming language is needed). >From my experience with the performance improvement task it looks like people avoid adding new queries for a specific need of a flow, instead they use the existing general ones (e.g. dao.getAllForX()) and do the actual join in the bll code. IMHO the proposed approach would simplify adding new specific queries and by that would prevent a decent part of performance issues in the future. I do not propose changing all existing SP's to inline queries in a once, but to allow adding new queries this way. Also we might consider converting relatively simple SP's to inline SQL statements later in a graduate way. [1] - https://gerrit.ovirt.org/#/c/74456 [2] - https://gerrit.ovirt.org/#/c/74458 Regards, Yevgeny

5 12

[ Announcment ] STD CI now supports custom junit reports
by Daniel Belenky 29 Mar '17

29 Mar '17

Hi all, The oVirt infra team is proud to announce that as from today the standard ci supports export of custom junit reports. *How to use?* Simply generate your junit .xml files, and follow the following naming: *<your_custom_name>.junit.xml. *Make sure you move them to exported-artifacts directory. That's all, the std ci will collect your .junit.xml files, and generate the junit report for you. Please feel free to contact the infra team on infra(a)ovirt.org for any more questions you have. Sincerely, -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

1 0