Project

General

Profile

Actions

Bug #15680

closed

Using bootdisk based imaging, the kickstart URL is always the foreman server, never a smart proxy

Added by Dylan Baars almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Details are here: https://groups.google.com/forum/#!topic/foreman-users/qmfr1UM6NZk

Summary is: After creating a new VM using the GUI, the ISO created is trying to download the kickstart file from the main katello server. Inspecting the kickstart file using the spoof address, everything in the kickstart is pointing at the capsule address for content etc,

https://wellkatellotst.niwa.local/unattended/provision?spoof=192.168.228.7

but there is no equivalent (kickstart provisioning address/file) on the capsule in the DMZ. I created an HTTP hole for a test VM to the katello server, booted and it started working - all content is downloaded from the capsule in the DMZ, but the kickstart file is stored on the main server. Is there a way to have the kickstart file be created and presented on the capsule that the server is being built from?

Actions

Also available in: Atom PDF