On Wed, Mar 20, 2019 at 12:45 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno mer 20 mar 2019 alle ore 11:07 Miguel Duarte de Mora Barroso <mdbarroso@redhat.com> ha scritto:
On Wed, Mar 20, 2019 at 9:43 AM Miguel Duarte de Mora Barroso
<mdbarroso@redhat.com> wrote:
>
> On Tue, Mar 19, 2019 at 6:51 PM Anton Marchukov <amarchuk@redhat.com> wrote:
> >
> > Retrigger failed, seems to be the same error [1]?
>
> OK, taking a look now.

I noticed that it is installing a very old openvswitch version in
fedora - 2.8.1 - as you can check in the logs [0].

17:21:51   openvswitch.x86_64 2.8.1-2.fc28
17:21:51   openvswitch-ovn-central.x86_64 2.8.1-2.fc28
17:21:51   openvswitch-ovn-common.x86_64 2.8.1-2.fc28
17:21:51   openvswitch-ovn-host.x86_64 2.8.1-2.fc28

The 'check-patch' scripts have also begun failing for all my patches
on all targets *except* 4.2 - check [1].

On el7, it is grabbing version openvswitch.x86_64
1:2.9.0-4.el7 from centos-ovirt-4.2-el7.

ovirt-provider-ovn *requires* openvswitch 2.10 on 4.3 *and* master.

Sandro, this is just a theory, but to me it looks like
ovirt-provider-ovn master doesn't "know" it needs to get the packages
from the virt7-ovirt-43-testing tag or something alike.

I would start with adding
Requires: openvswitch >= 2.10
to ovirt-provider-ovn spec file.

Then yes, looks like OST is taking openvswitch from the wrong repo.
Dafna, can you fix OST repo config for taking openvswitch from https://buildlogs.centos.org/centos/7/virt/$basearch/ovirt-4.3/ on EL7 and

Dafna is on sick leave,
In order to simplify the reposync file we dropped inlude list for all centos small repos so you won't need to handle whitelisting everything a new pkgs is out.
If a package is in multiple repos, YUM should bring always the highest version which is normal behavior for YUM afaik.
If there are specific repos you know for a fact you don't want pkgs taken from there, please add exclude from that repo.

I don't even see https://buildlogs.centos.org/centos/7/virt/$basearch/ovirt-4.3/ on reposync, is that a new repo?

 

If its needed for the project itself (check-patch) the project owner should update it in their automation/check-patch.fc28 file:


 

 

I've tried locally to revert patch [2] that added the 4.3 branch to
the provider; it fixed this, but I think that's just masking the
problem.

[0] - https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-on-merge/264/consoleFull
[1] - https://jenkins.ovirt.org/job/ovirt-provider-ovn_master_check-patch-el7-x86_64/611/
[2] - https://gerrit.ovirt.org/#/c/98565/

>
> >
> > [1] https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-on-merge/264/
> >
> > > On 19 Mar 2019, at 17:10, Anton Marchukov <amarchuk@redhat.com> wrote:
> > >
> > > I retriggered. Will see.
> > >
> > >> On 19 Mar 2019, at 16:25, Miguel Duarte de Mora Barroso <mdbarroso@redhat.com> wrote:
> > >>
> > >>> https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-on-merge/263/
> > >
> > > --
> > > Anton Marchukov
> > > Associate Manager - RHV DevOps - Red Hat
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Anton Marchukov
> > Associate Manager - RHV DevOps - Red Hat
> >
> >
> >
> >
> >
> >


--

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4GWFMJTRWF6Y427RNKXXZEKUBXF5K4IZ/


--

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA

TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)