Pulp

Thanks for filing this. Could you add any detail about specifically how the proxy settings were wrong? Was it a wrong hostname? Wrong port? Wrong auth credentials? Something else?

Also, could you add what specific proxy you were using, and what OS you were running Pulp on?

Thanks!

This issue can't be triaged without additional information asked in the previous comments.
Please specify the full command you ran in the steps to reproduce, so it will be clear what plugin yo use.

ttereshc wrote:

This issue can't be triaged without additional information asked in the previous comments.
Please specify the full command you ran in the steps to reproduce, so it will be clear what plugin yo use.

This happens if proxy configuration is used but no proxy is available.

I have experienced this behavior in my LAB with KVM machines, when preparing a pulp setup for a customer environment.

For recreation it should be suffice to just take a non-existing hostname as proxy host.

OS: Centos 7

Command used:

pulp-admin rpm repo update --proxy-host=proxy.example.com --proxy-port=8888 --repo-id=myrepo
pulp-admin rpm repo sync run --repo-id=myrepo