Project

General

Profile

Actions
Copy link

Bug #23291

closed

Proxy template URL not used for kickstart

Added by Adam Ruzicka over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Arend Lapere
Category:
Templates
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1624072
Pull request:
https://github.com/theforeman/foreman/pull/5822, https://github.com/theforeman/foreman/pull/5852, https://github.com/theforeman/foreman/pull/5853
Fixed in Releases:
1.18.1, 1.19.0
Found in Releases:
1.18.0-RC1, 1.18.0-RC2, 1.18.0-RC3
Red Hat JIRA:

Description

Steps to reproduce:
1) Have a smart-proxy with templates feature
2) Set template_url to use http in /etc/smart-proxy/settings.d/templates.yml
3) Assign the proxy to a subnet as template proxy
4) Try to provision a host in subnet from step 3

Actual result:
The host tries to access the proxy over the https and fails because CA used to signed the proxy's certificate is not trusted

Expected result:
template_url is honored and provisioning doesn't fail

After observing the log, we noticed that the base url is trying to access the templateServer API on the wrong URL: https://<proxy>:8443/unattended*/unattended* while it should be https://<proxy>:8443/unattended

Related issues 1 (0 open — 1 closed)

Has duplicate Foreman - Bug #24787: Templates subnet association renders to Capsule URL and not template_urlDuplicateLukas ZapletalActions
Actions
Copy link

Also available in: Atom PDF