Problem:
I have new foreman server running on CentOS 7.7.1908
I am trying to provision my 1st vmware vm that will run the same version of CentOS.
I followed instructions very thoroughly. Added the host correctly. Generated new MAC address if the new VM that just created on VMWARE workstation and added it to the host profile and dhcpd.conf
Contents of dhcp.conf:
[root@foreman dhcp]# cat dhcpd.conf
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.example
# see dhcpd.conf(5) man page
#
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.190 192.168.1.246;
}
host vmsev1rh7.nilelinux.lan {
hardware ethernet 00:50:56:33:DF:7D;
fixed-address 192.168.1.243;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254, 4.2.2.2;
option broadcast-address 192.168.1.255;
option subnet-mask 255.255.255.0;
option domain-name "nilelinux.lan";
next-server 192.168.1.242;
filename "pxelinux.0";
default-lease-time 600;
max-lease-time 7200;
}
When start new VM get this:
PXE-E53 No boot filename received
Expected outcome:
VM will boot up and get provisioned
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
foreman-1.17.4-1.el7.noarch
foreman-selinux-1.17.4-1.el7.noarch
foreman-release-1.17.4-1.el7.noarch
foreman-installer-1.17.4-1.el7.noarch
foreman-release-scl-7-1.el7.noarch
foreman-postgresql-1.17.4-1.el7.noarch
foreman-proxy-1.17.4-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.12.1-1.el7.noarch
foreman-debug-1.17.4-1.el7.noarch
foreman-cli-1.17.4-1.el7.noarch
Distribution and version:
CentOS Linux release 7.7.1908 (Core)
Other relevant data: