[ovirt-devel] [HEADS UP] ovift-engine: repository closure check on check-patch

[Sandro Bonazzola]

Hi,
with the following commits:
- https://gerrit.ovirt.org/71553
- https://gerrit.ovirt.org/71623

a minimal repository closure check is added to check-patches.sh.
Instead of performing a full blown repository closure, I limited the check
to the built rpms in oreder to reduce the risk of hitting repository
closure errors due to different projects.

This should help dropping the long time failing repository closure jobs
which are struggling to keep the pace with the changes we introduce in
master.
It should also help avoiding to merge patches which will break the
repository and the plain rpm  install flow.

The second patch switch from ovirt-master-release to experimental repo.
Here I need infra input, not sure experimental is the desired repo,
deisgned to replace ovirt-master-snapshot.

Thanks,
-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Vdsm build failure

[Piotr Kliczewski]

One more failure [1]

[1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/7610/console

On Mon, Feb 20, 2017 at 3:41 PM, Piotr Kliczewski
 wrote:
> Nir,
>
> I saw this issue in [1]:
>
> 10:20:12 FAIL: test_send_receive (storage_mailbox_test.TestMailbox)
> 10:20:12 
> --
> 10:20:12 Traceback (most recent call last):
> 10:20:12   File
> "/home/jenkins/workspace/vdsm_master_check-patch-fc25-x86_64/vdsm/tests/storage_mailbox_test.py",
> line 132, in test_send_receive
> 10:20:12 self.assertFalse(expired, 'message was not processed on time')
> 10:20:12 AssertionError: message was not processed on time
>
> it is something known?
>
> Thanks,
> Piotr
>
> [1] 
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc25-x86_64/1541/console
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] OST: HE installation on 4.1 fails due to default cluster level

[Martin Perina]

On Fri, Feb 24, 2017 at 11:58 AM, Sahina Bose  wrote:

> Hi all,
>
> The ovirt-engine 4.1 appliance has the Default cluster set to 4.2 and the
> hyperconverged OST tests fail here as the 4.1 host cannot be added to
> cluster.  (CLUSTER_VERSION_INCOMPATIBLE_WITH_CLUSTER)
>
> The appliance is from  http://resources.ovirt.org/
> repos/ovirt/tested/master/rpm/el7/noarch/ovirt-engine-
> appliance-4.1-20170215.1.el7.centos.noarch.rpm
>

​This is the tested master repository, so it should contain master code
where 4.2 cluster level is already default. So probably only
ovirt-engine-appliance version has not yet been bumped to 4.2 ...
​

​I'm just wondering why we don't have any ovirt-engine-appliance in latest
4.1 tested repo:

http://plain.resources.ovirt.org/repos/ovirt/tested/4.1/rpm/el7/noarch/
​
@Ryan?


>
> Has the default cluster level been changed in an updated appliance?
>
> Test results at http://jenkins.ovirt.org/view/oVirt system
> tests/job/ovirt_4.1_hc-system-tests/1/artifact/exported-artifacts
>
> thanks
> sahina
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] OST: HE installation on 4.1 fails due to default cluster level

[Sahina Bose]

Hi all,

The ovirt-engine 4.1 appliance has the Default cluster set to 4.2 and the
hyperconverged OST tests fail here as the 4.1 host cannot be added to
cluster.  (CLUSTER_VERSION_INCOMPATIBLE_WITH_CLUSTER)

The appliance is from
http://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/noarch/ovirt-engine-appliance-4.1-20170215.1.el7.centos.noarch.rpm

Has the default cluster level been changed in an updated appliance?

Test results at http://jenkins.ovirt.org/view/oVirt system
tests/job/ovirt_4.1_hc-system-tests/1/artifact/exported-artifacts

thanks
sahina
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel