I’m trying to auto-discovery a VM and it results with the attached picture.
Foreman and Proxy versions: 2.2
All Plugins have been installed using foreman-installer
It worked one time only with Success status and after rebooting the discovered host, it didn’t work again, also I tried another VMs and it didn’t work as well.
Network Configuration:
foreman-installer --foreman-proxy-dhcp true
–foreman-proxy-dhcp-managed true
–foreman-proxy-dhcp-gateway “192.168.217.2”
–foreman-proxy-dhcp-interface “ens33”
–foreman-proxy-dhcp-nameservers “192.168.217.107”
–foreman-proxy-dhcp-range “192.168.217.10 192.168.217.200”
–foreman-proxy-dhcp-server “192.168.217.107”
–foreman-proxy-dns true
–foreman-proxy-dns-managed true
–foreman-proxy-dns-forwarders “8.8.8.8; 4.4.4.4”
–foreman-proxy-dns-interface “ens33”
–foreman-proxy-dns-reverse “217.168.192.in-addr.arpa”
–foreman-proxy-dns-server “192.168.217.107”
–foreman-proxy-dns-zone “c9.com”
–enable-foreman-proxy
–foreman-proxy-tftp-managed true
–foreman-proxy-tftp=true \
Additional Info,
- No External Capsule.
- Gateway for Foreman Server VM 192.168.217.2 “NAT from VMware”
- Foreman Server IP 192.168.217.107 "VM on VMware