Project

General

Profile

Actions

Bug #37138

open

pulp_ansible shows wrong url in Galaxy install process

Added by David Sieg 4 months ago. Updated 3 months ago.

Status:
Need more information
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

We use Foreman Katello behind Loadbalancer due to more flexible certificate handling.
During installation process Galaxy Api redirects to origin hostname which isn't actual endpoint.

Is there any way to set correct url?

(ansible_2_15) user@domain.local ~/ansible () $ ansible-galaxy collection install microsoft.ad -f
Starting galaxy collection install process
Process install dependency map
Starting collection install process
Downloading https://internal.domain.local/pulp_ansible/galaxy/default/api/v3/plugin/ansible/content/ITSG/Library/custom/test_ansible_collection/test_rh_certified/collections/artifacts/microsoft-ad-1.4.1.tar.gz to /home/user/.ansible/tmp/ansible-local-1491441zo1sxs_e/tmpf679raqt/microsoft-ad-1.4.1-sv42uf7x
ERROR! Failed to download collection tar from 'mirrored_collections' due to the following unforeseen error: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)>. <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)>@

Actions #1

Updated by David Sieg 4 months ago

  • Category changed from Ansible Collections to API
Actions #2

Updated by David Sieg 4 months ago

  • Category changed from API to Repositories
Actions #3

Updated by Chris Roberts 4 months ago

  • Status changed from New to Need more information

Hi David,

Can you open your question on https://community.theforeman.org so more people can see it and we can provide help there, this redmine is more for bugs/features related to Katello.

Thanks!

Actions #4

Updated by Jeremy Lenz 3 months ago

  • Triaged changed from No to Yes
Actions #5

Updated by Jeremy Lenz 3 months ago

Load balancers are only supported with external smart proxies, not Foreman server's built-in smart proxy.

It's possible the issue may be resolvable thru pulp_ansible, if you'd like to open an issue there.

https://github.com/pulp/pulp_ansible

Actions

Also available in: Atom PDF