Foreman discovery unable to discover any host

Problem: I installed and configured foreman discovery 11 with foreman 1.17. All looks good but my discovered host list is empty. discovery feature is showing in the Active features list of my smart proxy also i have add discovery proxy in subnet but unable to discover any host.

[root@XX-XX-XX]# hammer discovery list
---|------|-----|------|--------|------------|------------|--------|------------
ID | NAME | MAC | CPUS | MEMORY | DISK COUNT | DISKS SIZE | SUBNET | LAST REPORT
---|------|-----|------|--------|------------|------------|--------|------------

Expected outcome: it should discovered the host in the given subnet

Foreman and Proxy versions: foreman 1.17 and discovery 11

Foreman and Proxy plugin versions: foreman 1.17 and discovery 11

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]

Hi,

Could you attach the server logs around the time one of the hosts you are trying to discover reboots?

Also, could you add a short description of your setup (are you using discovery in PXE or PEXLess mode? is your smart proxy also showing TFTP and DHCP in it’s list of features? did you select that smart proxy in your subnet for those features as well?).

Can you elaborate on the host please?

Have you read discovery manual? Foreman :: Plugin Manuals

now i able to discover hosts but stuck into new stuff

I am trying to add external puppet master master by following the doc but it throws multiple error without clue.

like below:

/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:185:in block in apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:232:inblock in benchmark’
/opt/puppetlabs/puppet/lib/ruby/2.4.0/benchmark.rb:308:in realtime' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:231:inbenchmark’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:184:in apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:369:inrun_internal’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:237:in block in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:inoverride’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:260:in override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:211:inrun’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:354:in apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:280:inblock (2 levels) in main’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:260:inoverride’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:280:in block in main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:inoverride’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:260:in override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:233:inmain’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:174:in run_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:inblock in run’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:661:in exit_on_fail' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:inrun’
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:inexecute’
/opt/puppetlabs/puppet/bin/puppet:5:in `’

is anyone one have any clue on it?