Failed to contact proxy, falling back to non-proxied config


Jobs are not accessing proxy anymore:

Failed to contact proxy, falling
back to non-proxied config


Sandro Bonazzola



Evgheni Dereveanchin
October 30, 2020, 6:43 PM

Since the initial proxy error has been resolved I propose moving further investigations to which has a more exact description of the issue that still persists. I will post future updates there to make the process less cluttered.

Ehud Yonasi
October 30, 2020, 10:10 AM

Adding pastebin of a reproducible error but then when I tried to delete the caches again, it did not reproduced.

Any inputs?

Ehud Yonasi
October 30, 2020, 7:56 AM

I’ve also found that inside the mock_runner try_proxy function it connects in el7 environment, there is the Using proxified config message in the console output.

But then after it launches the mock, it fails. so it might be a configuration issue, and yet I could not reproduce it in vm I took for testing (with and without caches).

Evgheni Dereveanchin
October 29, 2020, 9:14 PM

Thanks Ehud for revealing the error. This is EOL Fedora but still I've sent a patch to keep this from happening:

I've also logged in to the proxy to see why CentOS would fail and found out that there were timeouts reported for some of the upstream servers so I've increased caching to ensure we don't time out. All of these measures should help us get rid of the proxy error and investigate the actual root cause.

In case the fault is with non-proxied configs this should also help stabilize things although AFAIK we did see non-proxied mocks complete jobs successfully.

Ehud Yonasi
October 29, 2020, 2:36 PM is defined as proxy url and returns 404. let’s change it and see

Your pinned fields
Click on the next to a field label to start pinning.


Evgheni Dereveanchin


Sandro Bonazzola