Issue with node.rb on foreman

Support
1

Hello, I currently encounter an issue with the name resolution via node.rb
(foreman version 1.9)

We currently use the "external_node_v2.rb" in the
/usr/share/foreman-installer as the "/etc/puppet/node.rb' ('I think it's
done by default during the installation of foreman, I'm not sure because it
wasn't me who installed it).

The issue is that the name resolution works manually with
"/etc/puppet/node.rb hostname.example.com", or with the puppet agent
installed on server with a little of facts.
But when the server have a lot of facts information (like an hypervisor
with more than 10K lines), puppetagent give us an: "Error 400 on SERVER:
Failed when searching for node puppetUnix.localdomain: Failed to find
puppetUnix.localdomain via exec: Execution of '/etc/puppet/node.rb
puppetUnix.localdomain' returned 1".

Like you can see, our host is an unix host, so it's not due to the format,
nor a permissions issue (verified on each *.yaml file).

Does anyone has ever had this problem on a server with a lot of facts data?

2

> Hello, I currently encounter an issue with the name resolution via node.rb
> (foreman version 1.9)
>
> We currently use the "external_node_v2.rb" in the
> /usr/share/foreman-installer as the "/etc/puppet/node.rb' ('I think it's
> done by default during the installation of foreman, I'm not sure because it
> wasn't me who installed it).
>
> The issue is that the name resolution works manually with
> "/etc/puppet/node.rb hostname.example.com", or with the puppet agent
> installed on server with a little of facts.
> But when the server have a lot of facts information (like an hypervisor
> with more than 10K lines), puppetagent give us an: "Error 400 on SERVER:
> Failed when searching for node puppetUnix.localdomain: Failed to find
> puppetUnix.localdomain via exec: Execution of '/etc/puppet/node.rb
> puppetUnix.localdomain' returned 1".
>
> Like you can see, our host is an unix host, so it's not due to the format,
> nor a permissions issue (verified on each *.yaml file).
>
> Does anyone has ever had this problem on a server with a lot of facts data?
>

I'm guessing you are hitting a timeout on your puppet master executing the
node scrip? can you look at foreman logs while this happens? if thats the
case, you can add a timeout settings (that is used at
https://github.com/theforeman/puppet-foreman/blob/master/files/external_node_v2.rb#L44)

Ohad

··· On Wed, Jun 15, 2016 at 10:14 PM, Dam Olivier wrote:

–
You received this message because you are subscribed to the Google Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Yes you are right, it's a timeout issue.
We already have the timeout set on the script, and when i modify the "10"
(replaced by 20, 30 and 40), We have a "Timeout::Error".
I don't understand why we have this error because two weeks ago it was
working on the hosts.

··· Le jeudi 16 juin 2016 10:37:01 UTC+2, ohad a écrit : > > > > On Wed, Jun 15, 2016 at 10:14 PM, Dam Olivier > wrote: > >> Hello, I currently encounter an issue with the name resolution via >> node.rb (foreman version 1.9) >> >> We currently use the "external_node_v2.rb" in the >> /usr/share/foreman-installer as the "/etc/puppet/node.rb' ('I think it's >> done by default during the installation of foreman, I'm not sure because it >> wasn't me who installed it). >> >> The issue is that the name resolution works manually with >> "/etc/puppet/node.rb hostname.example.com", or with the puppet agent >> installed on server with a little of facts. >> But when the server have a lot of facts information (like an hypervisor >> with more than 10K lines), puppetagent give us an: "Error 400 on SERVER: >> Failed when searching for node puppetUnix.localdomain: Failed to find >> puppetUnix.localdomain via exec: Execution of '/etc/puppet/node.rb >> puppetUnix.localdomain' returned 1". >> >> Like you can see, our host is an unix host, so it's not due to the >> format, nor a permissions issue (verified on each *.yaml file). >> >> Does anyone has ever had this problem on a server with a lot of facts >> data? >> > > I'm guessing you are hitting a timeout on your puppet master executing the > node scrip? can you look at foreman logs while this happens? if thats the > case, you can add a timeout settings (that is used at > https://github.com/theforeman/puppet-foreman/blob/master/files/external_node_v2.rb#L44) > > > Ohad > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >