Unable to fetch my node definition

Support
1

Hi,
I have the following warnings in my host reports page.
I am not sure if it is related by i have just upgrade puppet master to
3.7.4 on my Foreman server.

BTW, running "/etc/puppet/node.rb pp3.mydomain.com" manually on Foreman
server works successfully

These are the permissions of node.rb
-r-xr-x— 1 puppet puppet 10730 Mar 3 14:21 /etc/puppet/node.rb

warningPuppetUnable to fetch my node definition, but the agent run will
continue:warningPuppetError 40 0 on SERVER: Failed to find pp3.mydomain.com
via exec: Execution of '/etc/puppet/node.rb pp3.mydomain.com' returned 1:

2

BTW,
Not sure if it the right think to check but i have tried to run node.rb as
foreman user and got permission denied

runuser -l foreman -c "/etc/puppet/node.rb pp3.mydomain.com"
cannot switch to user puppet, continuing as 'foreman'
Permission denied - /var/lib/puppet/yaml/foreman/pp3. mydomain.com.yaml

··· On Tuesday, March 17, 2015 at 9:15:48 AM UTC+2, Avi Tal wrote: > > Hi, > I have the following warnings in my host reports page. > I am not sure if it is related by i have just upgrade puppet master to > 3.7.4 on my Foreman server. > > BTW, running "/etc/puppet/node.rb pp3.mydomain.com" manually on Foreman > server works successfully > > These are the permissions of node.rb > -r-xr-x--- 1 puppet puppet 10730 Mar 3 14:21 /etc/puppet/node.rb > > warningPuppetUnable to fetch my node definition, but the agent run will > continue:warningPuppetError 40 0 on SERVER: Failed to find pp3.mydomain.com > via exec: Execution of '/etc/puppet/node.rb pp3.mydomain.com' returned 1: >
3

Just had this problem yesterday after upgrading from 1.7.2->.3 and found
the following issue:
http://projects.theforeman.org/issues/9673

Just use the workaround/solution in the pull request. It solved the
problem for us. After that we still had a problem but I think that was a
correct one but very confusing.
We had a hash parameter in a class and had set it in Foreman as
overriden but the type as set to yaml and the content to —{} which
resulted in the incorect yaml being send to the host resulting in an
error from the class. Maybe its related to the issue mentioned but I'm
not sure
More output or logs, didn't show anything after the patch, are available
if needed.

Regards,

Joop

··· On 17-3-2015 8:15, Avi Tal wrote: > Hi, > I have the following warnings in my host reports page. > I am not sure if it is related by i have just upgrade puppet master to > 3.7.4 on my Foreman server. > > BTW, running "/etc/puppet/node.rb pp3.mydomain.com"manually on Foreman > server works successfully >
4

Try running "tail -f /var/log/foreman/production.log" while running the
agent that is failing, what does it log?

··· On 17/03/15 07:15, Avi Tal wrote: > Hi, > I have the following warnings in my host reports page. > I am not sure if it is related by i have just upgrade puppet master to > 3.7.4 on my Foreman server. > > BTW, running "/etc/puppet/node.rb pp3.mydomain.com"manually on Foreman > server works successfully > > These are the permissions of node.rb > -r-xr-x--- 1 puppet puppet 10730 Mar 3 14:21 /etc/puppet/node.rb

–
Dominic Cleal
Red Hat Engineering

5

Hi,
I am using a formal release (foreman-1.7.2-1.el6.noarch) installed by RPM.
How can i install patch from pull request?

··· On Tuesday, March 17, 2015 at 9:48:56 AM UTC+2, jvandewege wrote: > > On 17-3-2015 8:15, Avi Tal wrote: > > Hi, > I have the following warnings in my host reports page. > I am not sure if it is related by i have just upgrade puppet master to > 3.7.4 on my Foreman server. > > BTW, running "/etc/puppet/node.rb pp3.mydomain.com" manually on Foreman > server works successfully > > Just had this problem yesterday after upgrading from 1.7.2->.3 and found > the following issue: > http://projects.theforeman.org/issues/9673 > > Just use the workaround/solution in the pull request. It solved the > problem for us. After that we still had a problem but I think that was a > correct one but very confusing. > We had a hash parameter in a class and had set it in Foreman as overriden > but the type as set to yaml and the content to ---{} which resulted in the > incorect yaml being send to the host resulting in an error from the class. > Maybe its related to the issue mentioned but I'm not sure > More output or logs, didn't show anything after the patch, are available > if needed. > > Regards, > > Joop > >
6

Started GET "/node/pp3.lab.mydomain.com?format=yml" for 172.29.100.100 at
2015-03-18 02:00:54 -0500
Processing by HostsController#externalNodes as YML
Parameters: {"name"=>"pp3.lab.mydomain.com"}
Rendered text template (0.0ms)
Completed 200 OK in 308ms (Views: 0.7ms | ActiveRecord: 22.5ms)

Started POST "/api/hosts/facts" for 172.29.100.100 at 2015-03-18 02:00:56
-0500
Processing by Api::V2::HostsController#facts as JSON
Parameters: {"certname"=>"pp3.lab.mydomain.com", "facts"=>"[FILTERED]",
"name"=>"pp3.lab.mydomain.com", "apiv"=>"v2",
:host=>{"name"=>"pp3.lab.mydomain.com", "certname"=>"pp3.lab.mydomain.com"}}
Import facts for 'pp3.lab.mydomain.com' completed. Added: 0, Updated: 7,
Deleted 0 facts
Completed 201 Created in 121ms (Views: 4.3ms | ActiveRecord: 0.5ms)

Started GET "/node/pp3.lab.mydomain.com?format=yml" for 172.29.100.100 at
2015-03-18 02:00:56 -0500
Processing by HostsController#externalNodes as YML
Parameters: {"name"=>"pp3.lab.mydomain.com"}
Rendered text template (0.0ms)
Completed 200 OK in 294ms (Views: 0.7ms | ActiveRecord: 23.0ms)

Started POST "/api/reports" for 172.29.100.100 at 2015-03-18 02:00:57 -0500
Processing by Api::V2::ReportsController#create as JSON
Parameters: {"report"=>"[FILTERED]", "apiv"=>"v2"}
processing report for pp3.lab.mydomain.com
Failed to send email notification puppet_error_state: ERF42-5670
[Foreman::Exception]: unable to find recipients
Imported report for pp3.lab.mydomain.com in 0.04 seconds
Completed 201 Created in 49ms (Views: 1.4ms | ActiveRecord: 0.0ms)

··· On Tuesday, March 17, 2015 at 6:38:50 PM UTC+2, Dominic Cleal wrote: > > On 17/03/15 07:15, Avi Tal wrote: > > Hi, > > I have the following warnings in my host reports page. > > I am not sure if it is related by i have just upgrade puppet master to > > 3.7.4 on my Foreman server. > > > > BTW, running "/etc/puppet/node.rb pp3.mydomain.com"manually on Foreman > > server works successfully > > > > These are the permissions of node.rb > > -r-xr-x--- 1 puppet puppet 10730 Mar 3 14:21 /etc/puppet/node.rb > > Try running "tail -f /var/log/foreman/production.log" while running the > agent that is failing, what does it log? > > -- > Dominic Cleal > Red Hat Engineering >