Re: [ovirt-devel] planned Gerrit maintenance

Maintenance completed successfully. Gerrit was upgraded to version 2.12.7 and a full reindex was performed. If you hit any issues that may be caused by the upgrade please let me know or open a Jira ticket. On Tue, Apr 4, 2017 at 12:28 AM, Evgheni Dereveanchin wrote: > Hi

[ovirt-devel] planned Gerrit maintenance

Hi everyone, I will be performing updates on gerrit.ovirt.org during the next hour. Within this period the UI and repositories may be unavailable. I will follow up as soon as maintenance activities are over. -- Regards, Evgheni Dereveanchin ___ Devel

Re: [ovirt-devel] Gluster/virt ports clarifications.

On Mon, Apr 3, 2017 at 5:51 PM, Sahina Bose wrote: > > > On Sun, Apr 2, 2017 at 7:23 PM, Leon Goldberg wrote: >> >> Hey, >> >> We're gathering information regarding the ports we open as part of the >> firewalld migration research. >> >> We have most of the

Re: [ovirt-devel] GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)

Sent a patch[1], installed ovirt-engine-webadmin-portal-debuginfo manually and the same error appears in the ui.log: 2017-04-03 12:51:49,285-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-7) [] Permutation name: C3D24A23286F7C8A99A2E725E808C153

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]

It looks like handling of units 'M' is missing in method mem.py javaX_mb. On Mon, Apr 3, 2017 at 5:52 PM, Barak Korren wrote: > Test failed: test_initialize_engine > > Link to suspected patches: > https://gerrit.ovirt.org/75054 > > Link to Job: >

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]

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:

Re: [ovirt-devel] oVirt in the new programming-journal

Great to see that! Kodus! On Mon, Apr 3, 2017 at 4:19 PM, Arik Hadas wrote: > 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

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 3/4/2017 ] [test_intialize_engine]

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:

Re: [ovirt-devel] Gluster/virt ports clarifications.

On Sun, Apr 2, 2017 at 7:23 PM, Leon Goldberg wrote: > Hey, > > We're gathering information regarding the ports we open as part of the > firewalld migration research. > > We have most of the current ports covered by either firewalld itself or by > 3rd party packages, however

[ovirt-devel] oVirt in the new programming-journal

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

Re: [ovirt-devel] GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)

On Mon, Apr 3, 2017 at 4:09 PM Nadav Goldin wrote: > Right. Missed that exclude, thanks. > I'll send a patch to include it from tested - all *debuginfo* packages > look like just a few MBs. > > +Guy Chen > > On Mon, Apr 3, 2017 at 3:55 PM, Greg Sheremeta

Re: [ovirt-devel] GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)

Hmm, I think *-debuginfo is explicitly excluded now. https://gerrit.ovirt.org/#/c/73497/8/common/yum-repos/ovirt-master.repo [ovirt-master-tested-el7] name=oVirt Master Latest Tested baseurl=http://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/ enabled=1 gpgcheck=0 max_connections=10

Re: [ovirt-devel] Gluster/virt ports clarifications.

On 04/02/2017 03:53 PM, Leon Goldberg wrote: > Hey, > > We're gathering information regarding the ports we open as part of the > firewalld migration research. > > We have most of the current ports covered by either firewalld itself > or by 3rd party packages, however some questions remain