Bug #35838
closed
syncing ansible-collections via http-proxy with auth fails
Description
When I want to synchronize an Ansible collection with an http proxy that uses auth it fails because apparently no auth is sent with it.
Steps to Reproduce:
1. set a Http-proxy (with auth) via UI
2. create a ansible-collections repo and use the proxy
3. Sync fails because of missing credentials (see screenshot)
Files
Updated by Samir Jha almost 2 years ago
- Target version set to Katello 4.8.0
- Triaged changed from No to Yes
Updated by Lucy Fu over 1 year ago
- Target version changed from Katello 4.8.0 to Katello 4.9.0
Updated by Samir Jha over 1 year ago
Did you need certs to authenticate the repo. Were you able to sync by providing those to the repo in the certs fields.
Updated by Samir Jha over 1 year ago
- Status changed from New to Need more information
- Triaged changed from Yes to No
Updated by Richard Stempfl over 1 year ago
Samir Jha wrote:
Did you need certs to authenticate the repo. Were you able to sync by providing those to the repo in the certs fields.
Hi, no i have ha http-proxy that uses username:password.
Like: http://username:password@http-proxy-fwdn:3128
I think this case is not covered in the code for ansible collections.
Updated by
Updated by Ian Ballou over 1 year ago
Richard, I cannot reproduce this on the latest Katello code.
What I did:
1) Create a squid proxy that requires basic auth
2) Create that HTTP proxy in Foreman and test the connection
3) Create an ansible collection repository with "Use specific HTTP Proxy" and sync it
Can you check the following:
1) Find the ID of your ansible collections repo. You can find it in the URL when you click on the repository.
2) Run the following in the console (`foreman-rake console`):
::Katello::Repository.find(<id of the repo>).backend_service(SmartProxy.pulp_primary).remote_options
3) Check the output to see if the proxy_url, proxy_username, and proxy_password make sense
If they do make sense, we'd need to debug further -- probably on community.theforeman.org under the support section. Please add the Katello flag.
Also, are you still on Katello 4.3.1? We're currently almost up to Katello 4.8 now, please try upgrading to at least Katello 4.5.
Updated by Ian Ballou over 1 year ago
- Status changed from Need more information to Rejected
- Target version changed from Katello 4.9.0 to Katello Recycle Bin
I'm going to close this for now since it cannot be reproduced. Please reopen if you have more data to provide.