Foreman Discovery unsucessful

Support
#1

Problem:
After a fresh installation of Katello 3.5 and Foreman 1.6, I was able to load the Bare metal into “Foreman Discovery” after network boot. However, the server keeps going into a loop with the error below. And that is why it never show up in the discovery host. Please advice.

Error: 
Could not determine Foreman instance, add kernel command option
Could not send facts to Foreman: undefined method 'host' fornil:NilClass
Fact cache invalid, reloading to foreman

Expected outcome:
Should show in the discover host, but never was successful.

Foreman and Proxy versions:
Foreman 1.16.2

Foreman and Proxy plugin versions:
Not sure how to find Proxy plugin versions. Please assist.

Other relevant data:
This is my default file for Foreman Discovery, not sure if I’m missing any thing.
[

# pwd
/var/lib/tftpboot/pxelinux.cfg
# cat default
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local


LABEL local
  MENU LABEL Default local boot
  MENU DEFAULT
  LOCALBOOT 0

LABEL discovery
MENU LABEL Foreman Discovery
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.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://10.0.210.2 proxy.type=foreman
IPAPPEND 2
#

]

#2

Hello,

enable root account, login and run discovery-debug and pastebin it somewhere. It looks like something is wrong with your kernel command line, maybe some invisible character like TAB or something? It looks good. Doublecheck spelling and compare to our docs. The FDI script is unable to read your foreman.url setting obviously.

#3

Hi Izap,

I re-installed the FDI script and it fixed the problem.

Thank you,
Sean