Also an interesting discussion to have is the same we had for maven cache

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 we
use mock.

Now I am not sure do we really need mock in ovirt system tests? As I
understand it uses lago and lago runs everything inside vms so it is
somehow isolated already?


On Thu, Dec 1, 2016 at 8:34 AM, Barak Korren <> wrote:

> 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/486c936a72b1d31db8b5892cb0c0372ba3c171509f168c1c24b5e32d5bf1
> 1861-primary.sqlite.xz
> > from ovirt-master-epel-el7: [Errno 256] No more mirrors to try.
> > 05:28:44
> >
> 486c936a72b1d31db8b5892cb0c0372ba3c171509f168c1c24b5e32d5bf1
> 1861-primary.sqlite.xz:
> > [Errno 14] HTTPS Error 404 - Not Found
> Looks like the sqlite index file got replaced while our test is running.
> We'll probably have to mirror to be resilient to this (Proxy cannot
> help you with something it did not proxy yet).
> One thing to note is that simple rsync mirror will not be enough, we
> will need a mirror system that will make _atomic_ updates to the
> mirror. Rsync will just make it behave like DS globalsync behaves.
> --
> Barak Korren
> RHCE, RHCi, RHV-DevOps Team

Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat
Infra mailing list

Reply via email to