inspector catalog not found

asked 2013-10-01 15:09:55 -0500

Sirex
21 ●1 ●1 ●4

background: We've been using puppet enterprise since 2.7, and have recently upgraded to 3.0.

I'm seeing some nodes fail their 'puppet inspect' cron job, with and error of:

Error: Could not run: Could not find catalog for (FQDN)

This is happening on several nodes, all of which were recently added. We added more that those which are giving errors though, so I don't think that's related, and certainly every node that's been in puppet for a good while isn't giving such errors.

I've tried doing a no-noop run on these nodes ... (more)

edit retag flag offensive close merge delete

Comments

Can you post the result of `facter fqdn` and `hostname -f`?

WhatsARanjit ( 2014-08-21 10:29:21 -0500 )edit

Try this. add the entry on your puppet.conf file on master side [main] modulepath=/etc/puppet/modules/

akshay ( 2015-04-16 01:40:00 -0500 )edit

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2015-09-14 03:34:34 -0500

jorhett
56 ●1 ●4

Well this is a bit old, but the same problem persists in Puppet 4. The problem is that it's looking for the catalog in YAML format, but later versions of Puppet 3 and Puppet 4 both store the catalog in JSON format. There's an open issue at https://tickets.puppetlabs.com/browse...