Project

General

Profile

Feature #26643

Allow to change mediapath for synced content to ip

Added by Dirk Götz about 1 year ago. Updated 9 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Provisioning
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

In one environment a separate installation network is required but in this network there is no dns server and no routing to the global dns, so we have to use ip addresses. When changing the foreman_url to ip, provisioning can find the templates but then fails when requesting the mediapath. For this use case it would be good if it is possible set the url to ip or foreman_url could affect the mediapath.

History

#1 Updated by James Jeffers about 1 year ago

  • Triaged changed from No to Yes
  • Target version set to Katello Backlog

#2 Updated by Partha Aji 11 months ago

Synced Content url media path is dynamically generated based on the smart proxy it points to. (https://github.com/Katello/katello/blob/master/app/models/katello/glue/pulp/repo.rb#L393-L411.)

Have you tried updating your smart proxy url to use ip address instead of FQDN ?

#3 Updated by Dirk Götz 10 months ago

I tried it right now, but I get a SSL verification error because the Smart proxy certificate only contains the FQDN and not the IP address.

Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([RestClient::SSLCertificateNotVerified]: SSL_connect returned=1 errno=0 state=error: certificate verify failed (error number 1)) for proxy https://192.168.200.2:9090/v2/features

#4 Updated by Partha Aji 10 months ago

Can you use http instead of https and confirm that runs. Use port 8000 instead of 9090 in the proxy url

#5 Updated by Jonathon Turel 9 months ago

  • Triaged changed from Yes to No

#6 Updated by Justin Sherrill 9 months ago

  • Triaged changed from No to Yes
  • Target version changed from Katello Backlog to Katello Recycle Bin
  • Status changed from New to Rejected

Oh i see the problem. You want to use an ip address for provisioning, but the 'smart proxy url' still needs to use ssl and thus a hostname. This is a feature, to be able to provision to a different URL than the smart proxy's hostname.

I don't see this feature being implemented any time soon, so iam going to close for now. Pull requests welcome though, we would accept this change and happily assist in someone making it.

Also available in: Atom PDF