VMware network kickstart

Support
1

Problem:

Foreman was configured with VMWare integration, Katello & DHCP:
foreman-installer --scenario=katello --foreman-proxy-tftp=true --foreman-proxy-dhcp=true --foreman-proxy-dhcp-interface=eth0 --foreman-proxy-dhcp-gateway=10.10.10.1 --foreman-proxy-dhcp-nameservers="10.11.11.11"

trying to kickstart VM in VMWare I get

24%20AM
24%20AM1130×524 32.2 KB

Expected outcome:

machine kickstarted and booted properly

Foreman and Proxy versions:

foreman-1.17.0-1.el7.noarch

Foreman and Proxy plugin versions:

foreman-1.17.0-1.el7.noarch
foreman-cli-1.17.0-1.el7.noarch
foreman-compute-1.17.0-1.el7.noarch
foreman-debug-1.17.0-1.el7.noarch
foreman-gce-1.17.0-1.el7.noarch
foreman-installer-1.17.0-1.el7.noarch
foreman-installer-katello-3.6.0-2.el7.noarch
foreman-postgresql-1.17.0-1.el7.noarch
foreman-proxy-1.17.0-1.el7.noarch
foreman-release-1.17.0-1.el7.noarch
foreman-release-scl-4-1.el7.noarch
foreman-selinux-1.17.0-1.el7.noarch
foreman-vmware-1.17.0-1.el7.noarch
tfm-rubygem-foreman_ansible-2.0.1-1.fm1_17.el7.noarch
tfm-rubygem-foreman_ansible_core-2.0.2-1.fm1_17.el7.noarch
tfm-rubygem-foreman_dhcp_browser-0.0.8-1.fm1_17.el7.noarch
tfm-rubygem-foreman_docker-4.0.0-1.fm1_17.el7.noarch
tfm-rubygem-foreman_remote_execution-1.4.5-2.fm1_17.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.0-1.fm1_17.el7.noarch
tfm-rubygem-foreman-tasks-0.11.2-1.fm1_17.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.4-1.fm1_17.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.12.0-2.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-6.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-3.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.12-2.fm1_17.el7.noarch

Other relevant data:

I can see DHCP request from the node with subsequent communication and no errors in logs

2

Is there a particular reason why you use grub2 pxeloader instead of pxelinux in a VM?

Do you see that error during initial boot or after OS was installed?

3

grub2 came by default. using pxelinux results in a different error. also Foreman displays an error: “Warning: This combination of loader and OS might not be able to boot.”

just changed settings to pxelinux disregarded warning and am getting boot loop with “Boot manager” asking what to boot and failing to boot with PXE

4

We need more detailed info.

5

what kind of info would you like to see @lzap?

6

Please elaborate this, be as verbose as possible.