Job fixed [1] with new SDKs.
Thanks.
[1] http://jenkins.ovirt.org/job/ovirt_master_system-tests/491/
On Tue, Sep 6, 2016 at 1:07 PM, Juan Hernández wrote:
> On 09/06/2016 10:37 AM, Eyal Edri wrote:
> > Glad to hear you found the issue!
> > Let me know when it's merged so we can publish it to th
Ovirt current version is 4.0.4 , How can i installed ovirt engine with older
version like 4.0.2.2 ? Could I install it by "yum install"?
Thank you.___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
On 09/06/2016 10:37 AM, Eyal Edri wrote:
> Glad to hear you found the issue!
> Let me know when it's merged so we can publish it to the nightlies and
> rerun the tests.
>
The fix for the master branch was merged. The artifacts (including RPMs)
are available in the output of the following jobs:
On 09/06/2016 11:49 AM, Yaniv Kaul wrote:
> Interesting that we don't see it on 4.0, saw it's a regression
> introduced somewhere, or a test case we have not seen before?
> Y.
>
It is a regression that was introduced recently in the master branch of
version 4 of the SDK. The patch that caused the
Interesting that we don't see it on 4.0, saw it's a regression introduced
somewhere, or a test case we have not seen before?
Y.
On Tue, Sep 6, 2016 at 11:37 AM, Eyal Edri wrote:
> Glad to hear you found the issue!
> Let me know when it's merged so we can publish it to the nightlies and
> rerun t
hi,Shlomo Ben David and Eyal Edri:
Is not the problem:
[maokx@maokx ~]$ date
Tue Sep 6 16:42:15 CST 2016
[maokx@maokx ~]$ getenforce
Permissive
[maokx@maokx ~]$ systemctl status iptables
● iptables.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
[maokx@
Glad to hear you found the issue!
Let me know when it's merged so we can publish it to the nightlies and
rerun the tests.
On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández wrote:
> On 09/05/2016 08:43 PM, Rafael Martins wrote:
> > - Original Message -
> >> From: "Juan Hernández"
> >> To:
Any update?
If we can't solve it soon, I suggest to revert the patch for running log
collector in the meantime, because we risk of having new regression coming
it,
and its our only way to verifying if master is broken or not.
Another option is to move master to work with API V4, which we should do
On 09/05/2016 08:43 PM, Rafael Martins wrote:
> - Original Message -
>> From: "Juan Hernández"
>> To: "Yaniv Kaul"
>> Cc: "Sandro Bonazzola" , "Rafael Martins"
>> , "Ondra Machacek"
>> , "devel"
>> Sent: Friday, September 2, 2016 2:31:42 PM
>> Subject: Re: [ovirt-devel] Failure in log c
Hi Maokexu,
Its seems that there is some iptables/firewall issue on your machine.
Please make sure that port 29418 (tcp) is open.
Best Regards,
Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL
RHCSA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011
Adding infra.
On Tue, Sep 6, 2016 at 10:01 AM, maok...@126.com wrote:
> hi,all:
> I have this issue when trying to connect to gerrit:
> [maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
> OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
> debug1: Reading configuration data /home/maokx/.ssh
hi,all:
I have this issue when trying to connect to gerrit:
[maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /home/maokx/.ssh/config
debug1: /home/maokx/.ssh/config line 1: Applying options for gerrit.ovirt.o
12 matches
Mail list logo
