On Thu, Sep 17, 2015 at 6:26 PM, Petr Horacek <phoracek@redhat.com> wrote:
but it seems like there is no openvswitch in it.

However, openstack-kilo is ok.

Just another question, is it ok if I add a
http://mirror.centos.org/centos/$releasever/cloud/$basearch/openstack-kilo/ instead?
it has openvswitch-2.3.1-2.el7.x86_64.rpm
I'd rather prefer to work with CentOS Cloud SIG there.

This will allow to rely on centos-release-openstack.noarch for CentOS Virt SIG oVirt releases.


 


Petr



2015-09-17 13:47 GMT+02:00 Sandro Bonazzola <sbonazzo@redhat.com>:


On Thu, Sep 17, 2015 at 1:11 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Thu, Sep 17, 2015 at 09:17:55AM +0200, Sandro Bonazzola wrote:
> *Hi:*
>
> *06:37:41* package: vdsm-hook-ovs-4.17.2-142.git932c120.el7.noarch
> from check-custom-el7
>
> *06:37:41*   unresolved deps:
>
> *06:37:41*      openvswitch >= 0:2
>
>
> http://jenkins.ovirt.org/job/repos_master_check-closure_merged/DISTRIBUTION=centos7/707/console
>
> Please provide the missing dependency or drop it ASAP.

Petr, we've forgotten about this job, apparently.

Sandro, can we exclude vdsm-hook-ovs from the closure job? It is still
rather a step-offstpring of Vdsm which is less acute to test.

However, can we instead add
    https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/
to the repos available to this job?


Juno? Aren't we using Kilo? And being master, what about Liberty?

 
    https://gerrit.ovirt.org/#/c/46135/3/automation/check-patch.repos.el7
attempts to do so to the per-patch rpm installation job.

Dan.



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com




--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com