About | FAQ | Help
Ask Your Question

node listed in "cert list --all" and defined in manifest but "could not find default node or by name"

asked 2014-02-03 16:37:04 -0500

bismark gravatar image

updated 2014-02-03 16:50:55 -0500

Stefan gravatar image

Please some master of puppets help me out with this:

I have a manifest in /etc/puppet/manifests/test-centos.pp (master) defining what I want for this node only. This node is listed in puppet cert list --all. (+ "test-centos.domain.com" CC:FC:AA:..)

node 'test-centos.domain.com' {
  file {'/tmp/test-centos.puppet':
        ensure => present,
        content => "test",

What I'm having in syslog is:

puppet-master - Could not find default node or by name with 'test-centos.domain.com' on node test-centos.domain.com.
  1. connectivity is ok, I can ping and ssh both hostnames
  2. I'm positive the names match
  3. include "node default ...
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2014-02-03 17:00:09 -0500

Stefan gravatar image

updated 2014-02-06 13:47:34 -0500

Please note that the puppetmaster will only load the manifest described with the manifest parameter which is /etc/puppet/manifests/site.pp by default. So you either have to move your node definition there or - if you want to keep them in seperate files - import the appropiate files inside site.pp. An example of the import statement can be found here


Note that if you use wildcards in site.pp (e.g. import 'nodes/*.pp') this glob is not evaluated each time an agent requests a catalog. That beeing said you have to do a touch site.pp whenever ... (more)

edit flag offensive delete link more


ok, I've included this node in my site.pp. It only worked when I revoked and requested a new cert for this node. Now I was trying to change ...(more)

bismark gravatar imagebismark ( 2014-02-04 11:44:13 -0500 )edit

can you verify that `puppet agent --configprint certname` returns the exact name that you use in your node manifest?

Stefan gravatar imageStefan ( 2014-02-04 13:02:06 -0500 )edit

it is. i've just double checked that. (master debian 2.7.18) (agent centos 2.7.9). Also tried to change the name of the file (test-centos.puppet to ...(more)

bismark gravatar imagebismark ( 2014-02-04 13:31:14 -0500 )edit

update: if I stop the puppet daemon /etc/init.d/puppet stop and manually ran "puppet agent --onetime" it works.. the configuration is finally applied.

bismark gravatar imagebismark ( 2014-02-04 16:12:28 -0500 )edit

It's working now. The definition for server=master... in /etc/puppet.conf (agent) was missing. .Just because certs were generated using that name I suppose.

bismark gravatar imagebismark ( 2014-02-05 13:45:58 -0500 )edit

answered 2014-02-04 14:55:22 -0500

Steve Shipway gravatar image

We found three distinct causes for manifests being apparently invisible to the puppetmaster.

  1. The manifest was not somehow included by site.pp This is mentioned in the previous answer. If you do not import the manifest explicitly, ot do a wildcard import for the directory that it is in, then puppet doesnt know about it.

  2. The file permissions were wrong, so the puppetmaster could not read the file The file needs to be readable by puppet, of course. Make sure it has the correct ownerships and read permissions.

  3. There exists a module with the same name as the containing directory ...

edit flag offensive delete link more


HI I have around 100 nodes. According to http://docs.puppetlabs.com/guides/scaling.html, WEBrick may be suffering at this scale (probably my case). I'm switching to passenger ...(more)

bismark gravatar imagebismark ( 2014-02-04 16:26:22 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2014-02-03 16:37:04 -0500

Seen: 1,343 times

Last updated: Feb 06 '14