It indeed looks like a repository issue - in the logs I see it failed
downloading some of the packages during reposync stage. Also I saw the
failures were on 2 different hosts, so it doesn't look like a slave
related issue.

I just re-triggered it [2] and it passed the reposync stage. Could it
be that repository is being updated during the time the job is
scheduled?


Nadav.





[1] http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/175/

On Wed, Jul 5, 2017 at 1:02 PM, Gil Shinar <gshinar@redhat.com> wrote:
> Gal/Nadav,
>
> Can you please assists with this issue?
>
> Thanks
> Gil
>
> On Wed, Jul 5, 2017 at 5:32 AM, <jenkins@jenkins.phx.ovirt.org> wrote:
>>
>> Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/
>> Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/171/
>> Build Number: 171
>> Build Status:  Failure
>> Triggered By: Started by timer
>>
>> -------------------------------------
>> Changes Since Last Success:
>> -------------------------------------
>> Changes for Build #171
>> [Eyal Edri] skip repo closure test for master suite
>>
>> [Barak Korren] Add job configuration for infra-ansible
>>
>> [Gil Shinar] Change project-pattern value in jjb deploy job
>>
>>
>>
>>
>> -----------------
>> Failed Tests:
>> -----------------
>> No tests ran.
>> _______________________________________________
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>