I have a new foreman installation on a virtual machine
we have an administration lan on eth0 and a deployement lan on eth1
i’ve changed the unattended url in foreman to 192.168.xxx.xxx who is the ip of the virtual machine on eth1
but I got curl (22) the requested url returned 404 when anadonca is trying to get the kickstart
eg failed to fetch kickstart from …
Expected outcome:
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)
2019-02-28T16:18:56 [I|app|b51d3] Processing by UnattendedController#host_template as TEXT
2019-02-28T16:18:56 [I|app|b51d3] Parameters: {“token”=>“bfe99873-286f-479a-8a7d-87e94fdaba22”, “kind”=>“provision”}
2019-02-28T16:18:56 [E|app|b51d3] unattended: unable to find a host that matches the request from 192.168.17.217
2019-02-28T16:18:56 [I|app|b51d3] Rendering text template
2019-02-28T16:18:56 [I|app|b51d3] Rendered text template (0.0ms)
2019-02-28T16:18:56 [I|app|b51d3] Completed 404 Not Found in 51ms (Views: 1.1ms | ActiveRecord: 7.4ms)
This should explain it. There is no such host in Foreman database that either has:
Enabled build mode and provisioning token set to bfe99873-286f-479a-8a7d-87e94fdaba22
Or IP address of the provision interface equal to 192.168.17.217
Therefore 404 is returned.
I highly recommend to avoid multihome Foreman setups, it’s a challenging and you will run into issues. Install Foreman on a host with single network interface.