On Thu, Oct 12, 2017 at 2:36 PM, Dafna Ron <dron@redhat.com> wrote:

Thank you.
I was not sure if this is repo related since I could not see a specific
package that it failed on.
Sandro believes this might have been a repo outage so I am opening a
ticket to try and investigate this issue and find the root cause.

https://ovirt-jira.atlassian.net/browse/OVIRT-1693

We have far too many repo outages.

I believe it could be partially solved by properly and consistently keeping the reposync up-to-date.

It's far from bullet-proof, and is annoying work, but we need to once every other week or so to just do it, to ensure we can perform offline installation (I don't believe it's a complete repo outage, but partial, which is why I think it'll help).

Thanks,
Dafna

On 10/12/2017 11:37 AM, Viktor Mihajlovski wrote:
> On 12.10.2017 12:27, Yaniv Kaul wrote:
>> Repo issues (again?)
>> See log[1].
>> Y.
>>
>> [1]
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3104/artifact/exported-artifacts/basic-suit-master-el7/003_00_metrics_bootstrap.py.junit.xml
>>
>> On Thu, Oct 12, 2017 at 12:26 PM, Dafna Ron <dron@redhat.com> wrote:
>>
> I agree, seems to be unrelated to my patch.
>