3:26 a.m.
This was probably due to the 4.2 publisher job failing ( timedout ).
It is now fixed and job should be back to normal.
BTW, you can also update the job to use the tested repo [1] which has all
the latest RPMs as well and has less chance of breaking.
[1] https://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/
On Fri, Apr 26, 2019 at 2:42 PM Milan Zamazal <mzamazal(a)redhat.com> wrote:
Sandro Bonazzola <sbonazzo(a)redhat.com> writes:
>
https://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_6...
>
>
> Not sure what happened but yesterday ovirt Node 4.2 jenkins job
> started failing with:
>
> 06:28:14,517 INFO program:Error: Package:
> vdsm-client-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot)
> 06:28:14,518 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7
> 06:28:14,518 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,519 INFO program:vdsm-api = 4.20.23-1.el7
> 06:28:14,520 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,521 INFO program:vdsm-api = 4.20.39.1-1.el7
> 06:28:14,522 INFO program:Error: Package:
> vdsm-jsonrpc-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot)
> 06:28:14,522 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7
> 06:28:14,523 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,524 INFO program:vdsm-api = 4.20.23-1.el7
> 06:28:14,525 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,526 INFO program:vdsm-api = 4.20.39.1-1.el7
> 06:28:14,527 INFO program:Error: Package:
> vdsm-python-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot)
> 06:28:14,528 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7
> 06:28:14,528 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,529 INFO program:vdsm-api = 4.20.23-1.el7
> 06:28:14,530 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch
> (ovirt-4.2-centos-ovirt42)
> 06:28:14,531 INFO program:vdsm-api = 4.20.39.1-1.el7
>
> Looking at vdsm.spec I see:
> grep "\-api" vdsm.spec.in:
> Requires: %{name}-api = %{version}-%{release}
> Requires: %{name}-api = %{version}-%{release}
> Obsoletes: %{name}-api < 4.16
> Requires: %{name}-api = %{version}-%{release}
> Requires: glusterfs-api >= %{gluster_version}
>
> Looking at the Obsoletes:
>
> %package jsonrpc
> Summary: VDSM API Server
> BuildArch: noarch
> Requires: %{name}-python = %{version}-%{release}
> Requires: %{name}-api = %{version}-%{release}
> Requires: %{name}-yajsonrpc = %{version}-%{release}
> Obsoletes: %{name}-api < 4.16
>
> There's an Obsoletes without a Provides while there are still around
lines
> with:
> Requires: %{name}-api = %{version}-%{release}
>
> so I don't know how it could have worked till now.
"Obsoletes: vdsm-api" is probably just some old forgotten stuff.
vdsm-api is still being built and used, including recent 4.20.*
versions. The problem above looks like there is a package version
mismatch in some repos, for a different reason than the package wouldn't
be built.
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)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/E5I5PWYVPJ2...
--
Eyal edri
MANAGER
RHV/CNV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)