[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23305#comment-23305 ] eyal edri [Administrator] commented on OVIRT-869: ------------------------------------------------- bq. Port 5000 is where the python script is running no? So the Squid had an issue resolving the name of the very host it is running on? We should probably just resolve this forever by placing the name in /etc/hosts on the proxy server.... It currently has :127.0.0.1 proxy.phx.ovirt.org Do you mean adding the public IP address as well? bq. Typically the failures we're seeing are because of failures in the origin mirror we are actually proxying (Fedora and EPEL seem to be notoriously non-atomic when updating their mirrors). The way to solve this is only to used fully-fledged mirrors instead of a proxy (But this takes more maintenance and more storage). By full fledged mirrors you mean have it on resources.ovirt.org ? will we need Katello to manage them or mirror with rsync will suffice?

Investigate proxy errors from proxy.phx.ovirt.org -------------------------------------------------

Key: OVIRT-869 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest

We need to make sure jobs don't fail on proxy like [1]. Either use original repos if proxy is down or add watchdog / alerts for the proxy service. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artifa...

-- This message was sent by Atlassian JIRA (v1000.571.2#100021)