Bug #15680
closed
Using bootdisk based imaging, the kickstart URL is always the foreman server, never a smart proxy
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?
Updated by Dominic Cleal over 8 years ago
I think you're describing the Template feature of the smart proxy (https://theforeman.org/manuals/1.12/index.html#4.3.12Templates), but I don't recommend using it. It ought to be used if enabled and applicable to the host.
Updated by Dylan Baars over 8 years ago
Dominic Cleal wrote:
I think you're describing the Template feature of the smart proxy (https://theforeman.org/manuals/1.12/index.html#4.3.12Templates), but I don't recommend using it. It ought to be used if enabled and applicable to the host.
Ahhh! Thanks for the link, I've got it working (had to install a tftp server and enable tftp for the foreman-proxy). Why do you not recommend doing this? It seems to work well.
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Resolved
Just that the implementation is awful, glad it works for you.