On Saturday, September 27, 2014 4:52:16 PM UTC-5, bluethundr wrote: > > Hello, > > When I tried adding a node to my puppet server running puppet 3.7.1 (on > both server and the client) I'm getting an error stating that puppet can't > find the node definition: > > Warning: Unable to fetch my node definition, but the agent run will > continue: > > Warning: Error 400 on SERVER: Failed to find ops.mydomain.com via exec: > Execution of '/etc/puppet/node.rb ops.mydomain.com' returned 1: > > Info: Retrieving pluginfacts > > Info: Retrieving plugin > > Info: Loading facts > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Failed when searching for node ops.mydomain.com: Failed to find > ops.mydomain.com via exec: Execution of '/etc/puppet/node.rb > ops.mydomain.com' returned 1: > > Warning: Not using cache on failed catalog > > Error: Could not retrieve catalog; skipping run > > I have a nodes manifest from an earlier version of puppet (version 3.4.3) > tht used to work well that I tried to include in this version of puppet. > > > Based on the above error I tried to include the nodes.pp file like this > from within the /etc/puppet/node.rb like this. >
By its name and apparent use, node.rb is an external node classifier *program*, written in *Ruby*. It is not a Puppet manifest, so the Puppet DSL documentation does not apply to it. It may be that you want instead to modify /etc/puppet/manifests/site.pp, but given that there is an ENC in the picture, you really ought to get a grip on how your nodes are being classified before deciding how best to add a new one. John -- 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/9651ead7-84ba-4efb-910d-57bc21440bfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
