You are right, I had couple of parameters which is not in that module and caused the problem. Even after removing those parameters, the issue was not resolved because I had environment_timeout = unlimited and that did not flush my environment cache. To resolve that I changed the environment_timeout = 0 and restarted the puppetserver service.
Thank you for your help! Now after fixing all those parameters I a got into different error. Since the new error is different, I will go ahead and create another topic. Regards Sankara On Thursday, December 8, 2016 at 4:24:59 AM UTC-8, Greg Sutcliffe wrote: > > On 6 December 2016 at 19:40, Sankara <saras...@gmail.com <javascript:>> > wrote: > > While running “puppet agent -t” (to install and configure > foreman-proxy) , I am getting the below error on my node. Can you please > help me to find what could be the issue? > > > > Error: Could not retrieve catalog from remote server: Error 400 on > SERVER: Invalid parameter dns_realm on Class[Foreman_proxy] at > /dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local > > Warning: Not using cache on failed catalog > > Error: Could not retrieve catalog; skipping run > > Looking at > https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/init.pp > > the $dns_realm parameter isn't exposed for configuration - it's only used > within params.pp to set $dns_tsig_principal (which *is* available in > init.pp). Feel free to submit a bug or even send a patch if you feel that > behaviour is wrong :) > > Cheers > Greg > -- > Greg Sutcliffe > Community Lead, Foreman > IRC: gwmngilfen > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e64c8ed3-3fb5-4d26-b451-411f7d4fa3b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.