>
>
> You understand wrong. The cache dir (/var/lib/lago) is bind-mounted
> into mock, so it persists across runs.
>
This is interesting cause I see it constantly downloads some RPMs each run.
Maybe repos updated that fast then it makes sense. Will take a look during
debug.
>
> > Now I am not sur
>
>
> This is IMO miss-diagnosing the issue - the problem is not a failed
> mirror - the problem is 404 on getting a metadata file from a mirror
> that was updated because you have a stale repomd.xml file on your
> local cache. Another mirror will not help there because it would
> probably be updat
On Thu, Dec 1, 2016 at 10:17 AM, Barak Korren wrote:
> On 1 December 2016 at 09:43, Anton Marchukov wrote:
> > Hello All.
> >
> > Let's try not to over-complicate this. The error here we should care
> about
> > is "no more mirrors to try" Just use more than one mirror in yum
> > configuration in
On 1 December 2016 at 10:14, Anton Marchukov wrote:
> Also an interesting discussion to have is the same we had for maven cache
> files.
>
> We use reposync in lago that is supposed to sync repos locally and then it
> can update the existing cache to match the remote mirror when it is invoked,
> t
On 1 December 2016 at 09:43, Anton Marchukov wrote:
> Hello All.
>
> Let's try not to over-complicate this. The error here we should care about
> is "no more mirrors to try" Just use more than one mirror in yum
> configuration in ovrit system tests. That's what we enabled in standard ci
> and it w
Also an interesting discussion to have is the same we had for maven cache
files.
We use reposync in lago that is supposed to sync repos locally and then it
can update the existing cache to match the remote mirror when it is
invoked, then as I understand we get its cache deleted each time because w
Hello All.
Let's try not to over-complicate this. The error here we should care about
is "no more mirrors to try" Just use more than one mirror in yum
configuration in ovrit system tests. That's what we enabled in standard ci
and it works fine there (although we are not running this new config for
On 1 December 2016 at 09:26, Eyal Edri wrote:
> Will this error get solved also by the patch for replacing the proxies?
> Or we need to mirror epel to oVirt to avoid such errors?
>
> 05:28:44 and following error: Error setting up repositories: failure:
> repodata/486c936a72b1d31db8b5892cb0c0372ba3
Will this error get solved also by the patch for replacing the proxies?
Or we need to mirror epel to oVirt to avoid such errors?
ovirt-master-epel-el7/primary_ FAILED
*05:28:44*
(10/12): ovirt-master-epel 2% [ ] 0.0 B/s | 482 kB --:-- ETA
ovirt-master-epel-el7/primary_
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3801/,
Build Number: 3801,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
10 matches
Mail list logo
