Warning: anaconda: failed to fetch kickstart http://foremanserver.domain/unattended/provision

Disclaimer, I’m new to Foreman, and relatively inexperienced with any kind of Linux deployment.

I’ve installed Foreman 3.3 with the Katello scenario with the goal of deploying Centos 7 and 8 workstations/servers.

I’ve followed the provisioning guide, but I’m getting stuck at this point

Problem:
Warning: anaconda: failed to fetch kickstart http://foremanserver.domain/unattended/provision

My DHCP is running from a Windows server (we’ve got a bunch of subnets all managed from one DC), which I believe is working fine, as I get an IP, a splash screen and the Centos Bootloader starts up, until I hit the error above.

My foreman server has a fqdn, which I can resolve and ping from the dracut prompt, so I assume that means it’s not a DHCP/DNS issue (I mean, it’s definitely going to be DNS obviously…!)

I can’t browse to http://foremanserver.domain/unattended/ in a browser, I assume I should be able to…?!

Any help would be greatly appreciated!

Here are my versions:

Foreman and Proxy versions:

[root@deploy01 ~]# rpm -qa | grep foreman
foreman-installer-katello-3.3.0-1.el8.noarch
foreman-cli-3.3.0-1.el8.noarch
rubygem-hammer_cli_foreman_tasks-0.0.17-1.fm3_2.el8.noarch
foreman-proxy-3.3.0-1.el8.noarch
foreman-release-3.3.0-1.el8.noarch
foreman-installer-3.3.0-1.el8.noarch
rubygem-foreman_templates-9.3.0-1.fm3_3.el8.noarch
foreman-service-3.3.0-1.el8.noarch
rubygem-foreman-tasks-6.0.2-1.fm3_3.el8.noarch
foreman-debug-3.3.0-1.el8.noarch
foreman-3.3.0-1.el8.noarch
foreman-dynflow-sidekiq-3.3.0-1.el8.noarch
rubygem-foreman_remote_execution-7.1.0-1.fm3_3.el8.noarch
rubygem-foreman_maintain-1.1.1-3.el8.noarch
rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman-3.3.0-1.el8.noarch
foreman-postgresql-3.3.0-1.el8.noarch

A friendly suggestion: Foreman is a beast, it’s swiss knife with 99 blades really. I highly suggest to start small, build a small deployment with automated installation via static files or a script or whatever and gradually build on top of that switching to Foreman later.

Having said that, here you need to investigate why the kickstart was not rendered correctly, see production.log. Check your network, DNS, firewalls as well, the host might not be able to reach foremant at all. It is hard to tell, there are dozens of things that can break.

Thanks for the reply. I managed to get it working with a fresh (probably my fourth!) install!