Test failed: 000_check_repo_closure.check_repo_closure Link to suspected patches: Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ 4.1/1783 Link to all logs: http://jenkins.ovirt.org/job/ test-repo_ovirt_experimental_4.1/1783/testReport/junit/( root)/000_check_repo_closure/check_repo_closure/ Error snippet from the log: package: cockpit-ostree-138-1.el7.x86_64 from internal_repo unresolved deps: /usr/libexec/rpm-ostreed package: python2-botocore-1.4.43-1.el7.noarch from internal_repo unresolved deps: python-dateutil >= 0:2.1 We seem to have two new repoclosure problems here. 1. The first one is due to python2-botocore from http://mirror.centos.org/ centos/7/virt/x86_64/ovirt-4.0/common/ now requiring python-dateutils version 2.1 while we have only 1.5 in our dependencies.

2. The second one might be just a missing include in OST. Which package/repo should we consume rom-ostreed from?

Anton. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

On Wed, Jun 28, 2017 at 11:12 AM, Anton Marchukov <amarchuk(a)redhat.com&gt; wrote: > Test failed: 000_check_repo_closure.check_repo_closure > > Link to suspected patches: > > Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4. > 1/1783 > > Link to all logs: http://jenkins.ovirt.org/job/t > est-repo_ovirt_experimental_4.1/1783/testReport/junit/(root) > /000_check_repo_closure/check_repo_closure/ > > > Error snippet from the log: > > package: cockpit-ostree-138-1.el7.x86_64 from internal_repo > unresolved deps: > /usr/libexec/rpm-ostreed > package: python2-botocore-1.4.43-1.el7.noarch from internal_repo > unresolved deps: > python-dateutil >= 0:2.1 > > > We seem to have two new repoclosure problems here. > > 1. The first one is due to python2-botocore from > http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.0/common/ now > requiring python-dateutils version 2.1 while we have only 1.5 in our > dependencies. > Thanks, tagged python-dateutils for release: http://cbs.centos. org/koji/buildinfo?buildID=12099 But why are you using 4.0 Virt SIG repos in a 4.1 job? It doesn't make sense. > > 2. The second one might be just a missing include in OST. Which > package/repo should we consume rom-ostreed from? > rpm-ostree is available in CentOS Atomic SIG repo. We can't disable the cockpit-ostree subpackage build in VIrt SIG for providing recent cockpit but we don't really want to tag rpm-ostreee in virt sig repo. It's shipped in testing repo for atomic here: https://buildlogs. centos.org/centos/7/atomic/x86_64/ I would suggest to use Virt SIG as lookaside repo insead of as checked repo.

On Wed, Jun 28, 2017 at 11:12 AM, Anton Marchukov <amarchuk(a)redhat.com&gt; > wrote: > >> Test failed: 000_check_repo_closure.check_repo_closure >> >> Link to suspected patches: >> >> Link to Job: http://jenkins.ovirt.org/job/t >> est-repo_ovirt_experimental_4.1/1783 >> >> Link to all logs: http://jenkins.ovirt.org/job/t >> est-repo_ovirt_experimental_4.1/1783/testReport/junit/(root) >> /000_check_repo_closure/check_repo_closure/ >> >> >> Error snippet from the log: >> >> package: cockpit-ostree-138-1.el7.x86_64 from internal_repo >> unresolved deps: >> /usr/libexec/rpm-ostreed >> package: python2-botocore-1.4.43-1.el7.noarch from internal_repo >> unresolved deps: >> python-dateutil >= 0:2.1 >> >> >> We seem to have two new repoclosure problems here. >> >> 1. The first one is due to python2-botocore from >> http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.0/common/ now >> requiring python-dateutils version 2.1 while we have only 1.5 in our >> dependencies. >> > > Thanks, tagged python-dateutils for release: http://cbs.centos.org > /koji/buildinfo?buildID=12099 > But why are you using 4.0 Virt SIG repos in a 4.1 job? It doesn't make > sense. > > > >> >> 2. The second one might be just a missing include in OST. Which >> package/repo should we consume rom-ostreed from? >> > > rpm-ostree is available in CentOS Atomic SIG repo. We can't disable > the cockpit-ostree subpackage build in VIrt SIG for providing recent > cockpit but we don't really want to tag rpm-ostreee in virt sig repo. > It's shipped in testing repo for atomic here: https://buildlogs.centos > .org/centos/7/atomic/x86_64/ > > I would suggest to use Virt SIG as lookaside repo insead of as checked > repo. > Virt SIG is a lookaside repo, the only repo that is being checked it the internal_repo. We could exclude cockpit-ostree from the reposync file (as it was done in master yesterday)

-- DANIEL BELENKY Associate sw engineer RHEV DEVOPS Red Hat Israel <https://www.redhat.com/> dbelenky(a)redhat.com IRC: #rhev-integ, #rhev-dev <https://red.ht/sig>