Foreman Discovery Plugin
I have edited the PXE global default template like this:
LABEL discovery
MENU LABEL Foreman Discovery
MENU DEFAULT
KERNEL boot/fdi-image-rhel_7-vmlinuz
APPEND initrd=boot/fdi-image-rhel_7-img rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset proxy.url=https://mysat:9090 proxy.type=proxy
IPAPPEND 2
Before I edited the template I took the iso from the tftpboot directory on the sat server and mounted it on a VM to test. When I start up the VM I select Manual Network put in my network information (we don't use DHCP) and its awaiting the kexec. It shows up in my Discovered Host I click on "Provision" and change the Name and Select the appropriate host group and click submit.
The VM reboots and brings me right back to the "Manual Network" setup again instead of starting the install of the OS. I know I'm doing something wrong. Could someone please help.
After I changed the template and click "Build Default PXE" do I need to get the new image from the Sat Server.
Thanks
Responses
Hello,
have you associated Red Hat Kexec template with the OS which is selected for the Host you are provisioning? If the template is not found, then Satellite falls back to reboot instead of kexec which indeed ends up in a loop without DHCP.
Second, if you don't use DHCP, then you can't leverage PXE protocol and use Discovery via PXE. The only option is to use it in PXE-less mode (mount the ISO and boot from it)
Also, in your snippet I see the proxy.url points to "mysat" with port 9090. This port is used on Capsule, if this is hostname of Satellite server, the port is 443. Check the product documentation for more details.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
