[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira... ] Barak Korren commented on OVIRT-869: ------------------------------------ {quote} It currently has :127.0.0.1 proxy.phx.ovirt.org Do you mean adding the public IP address as well? {quote} If it has this already then the error is strange indeed, all I can think of is that maybe the mock environment running the failed job was not configured correctly (Trying to use the proxy repo URLs without setting it up as an HTTP proxy _in addition to_ not having proper _DNS_ config. If it was justh the HTTP proxy setting I would expect to see a "_connection refused_" error rather then "_could not resolve_"). {quote} 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? {quote} Not necessarily on resources.ovirt.org, we could (and maybe should) use a different server for that. WRT the mirroring solution itself we have many options with varying degrees of automation, features and required effort: # rsync (though not all upsreams may allow this kind of access) # yum reposync # repoman # Pulp # Artifactory # Katello The benefit of Katello would be in allowing us to control exactly which packages get tested by leveraging the work flow environments and the content views, but we could build comparable solutions with other tools. -- This message was sent by Atlassian JIRA (v1000.571.2#100021)