[ovirt-devel] Re: repoman glitch?

On 8 August 2018 at 22:53, Dan Kenigsberg <danken(a)redhat.com&gt; wrote: > > I've executed > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/3053/parameters/ > using > http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_6... > as customer repo. > > The custom repo has vdsm-4.20.36-11.git9f9bbcc.el7.x86_64.rpm which I > expected would be pulled onto ost hosts. However > > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/3053/artifact/expo... > shows that this was not the case. > > Any idea why is that? I can see the following in lago.log (in the section that includes the repoman log): 2018-08-08 18:47:02,357::INFO::repoman.common.repo::Resolving artifact source http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_6... 2018-08-08 18:47:02,493::INFO::repoman.common.sources.jenkins::Parsing jenkins URL: http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_6... 2018-08-08 18:47:02,493::WARNING::root:: No artifacts found 2018-08-08 18:47:02,493::INFO::root:: Done The fact that the log says 'Parsing jenkins URL' means that repoman properly detects that it is a URL to a Jenkins build, additionally when I run the following locally it seems to download the packages just fine: repoman ~/tmp/repo add http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_6... So this looks like a repoman bug. Adding Anton. @Dan - can you just retry?