Re: [ovirt-devel] [vdsm][maintainership] proposal for a new stable branch policy

2018-03-21 Thread Milan Zamazal
Francesco Romani writes: > Recently Milan, Petr and me discussed the state of ovirt.4.2, > considering that release 4.2.2 is still pending and this prevents > merging of patches in the sub-branch ovirt-4.2. > > We agreed we could improve the handling of the stable branch(es),

Re: [ovirt-devel] UI is not coming up after pulled latest code from master

2018-03-21 Thread Benny Zlotnik
Had this issue too (FF & Chrome), I've recompiled, ran engine-setup again and it resolved On Wed, Mar 21, 2018 at 3:01 PM, Greg Sheremeta wrote: > That message is probably not related, and is generally harmless. Compile > with

Re: [ovirt-devel] UI is not coming up after pulled latest code from master

2018-03-21 Thread Greg Sheremeta
That message is probably not related, and is generally harmless. Compile with DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" to stop that message. Does it work in firefox? Please share your ui.log from the server. Greg On Wed, Mar 21, 2018 at 8:55 AM, Gobinda Das

[ovirt-devel] UI is not coming up after pulled latest code from master

2018-03-21 Thread Gobinda Das
Hi, UI keeps on loading and I can see below error in browser. webadmin-0.js:422 Wed Mar 21 14:59:47 GMT+530 2018 com.google.gwt.logging.client.LogConfiguration SEVERE: Possible problem with your *.gwt.xml module file. The compile time user.agent value (gecko1_8) does not match the runtime

Re: [ovirt-devel] [vdsm] network test failure

2018-03-21 Thread Edward Haas
On Wed, Mar 21, 2018 at 12:15 PM, Petr Horacek wrote: > I tried to retrigger the build several times, it was always executed on > el7 machine, maybe it picks fc26 only when all other machines are taken? > > Shouldn't be "Permission denied" problem detected in >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

2018-03-21 Thread Dafna Ron
The patch was reported to cause 3 different issues but I cannot say for sure that the notifier error was actually one of them. I can say that all issues from master and 4.2 were cleared once the fix from Shmuel was merged and tested in cq. On Wed, Mar 21, 2018 at 10:28 AM, Michal Skrivanek <

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

2018-03-21 Thread Michal Skrivanek
> On 20 Mar 2018, at 10:33, Yaniv Kaul wrote: > > > > On Tue, Mar 20, 2018 at 9:49 AM, Michal Skrivanek > > wrote: > I’m not sure what is that test actually testing, if it depends on the > previous host

Re: [ovirt-devel] [vdsm][maintainership] proposal for a new stable branch policy

2018-03-21 Thread Yedidyah Bar David
On Wed, Mar 21, 2018 at 11:57 AM, Francesco Romani wrote: > Hi all, > > > Recently Milan, Petr and me discussed the state of ovirt.4.2, > considering that release 4.2.2 is still pending and this prevents > merging of patches in the sub-branch ovirt-4.2. > > We agreed we could

Re: [ovirt-devel] [vdsm] network test failure

2018-03-21 Thread Petr Horacek
I tried to retrigger the build several times, it was always executed on el7 machine, maybe it picks fc26 only when all other machines are taken? Shouldn't be "Permission denied" problem detected in link_bond_test.py:setup_module()? It runs "check_sysfs_bond_permission". 2018-03-20 18:12

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 19-03-2018 ] [002_bootstrap.add_instance_type ]

2018-03-21 Thread Dafna Ron
This issue was resolved on 4.2 and master. Thank you for resolving it quickly. On Mon, Mar 19, 2018 at 6:46 PM, Shmuel Melamud wrote: > Here is the fix: https://gerrit.ovirt.org/#/c/89187/ > > On Mon, Mar 19, 2018 at 4:12 PM, Dafna Ron wrote: > > thank you

[ovirt-devel] [vdsm][maintainership] proposal for a new stable branch policy

2018-03-21 Thread Francesco Romani
Hi all, Recently Milan, Petr and me discussed the state of ovirt.4.2, considering that release 4.2.2 is still pending and this prevents merging of patches in the sub-branch ovirt-4.2. We agreed we could improve the handling of the stable branch(es), in order to make the process smoother and