I can confirm that metadata is not cached in Squid settings. Closing this and will work on instead to improve stability.

In this case I don't see how. In a generic case, I thought we wanted to remove it completely replacing it with the 'new' squid script feature

can we try to improve the error log so it'll show if there is a problem with the mirrors?

The metadata is not cached. Most probably it's an issue with the original mirror (I have those issues once a week, each time they are updated)

David Caro

El 25/3/2016 8:09 a. m., "sbonazzo (oVirt JIRA)" <jira@ovirt-jira.atlassian.net> escribió:

sbonazzo created OVIRT-452:
------------------------------
Summary: please don't cache repositories metadata on proxy.phx.ovirt.org
Key:
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-452
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra

DEBUG util.py:393: Total download size: 239 M
DEBUG util.py:393: Installed size: 817 M
DEBUG util.py:393:
http://proxy.phx.ovirt.org:5000/fedora/22/x86_64/Packages/b/bridge-utils-1.5-10.fc22.x86_64.rpm:
[Errno -1] Package does not match intended download. Suggestion: run yum
--enablerepo=fedora clean metadata
DEBUG util.py:393: Trying other mirror.
DEBUG util.py:393: Error downloading packages:
DEBUG util.py:393: bridge-utils-1.5-10.fc22.x86_64: [Errno 256] No more
mirrors to try.
DEBUG util.py:515: Child return code was: 1

is causing NGN build failures

Jobs: ovirt-node-ng_ovirt-*_build-artifacts-fc22-x86_64/

–
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

–
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)