Quantcast
Channel: Ask Puppet: Puppet DevOps Q&A Community - RSS feed
Viewing all articles
Browse latest Browse all 6104

"Unable to fetch my node definition" and "Could not find terminus rest for indirection node" after upgrade from Puppet 3.8 to 4.7

$
0
0
After upgrading our Puppet environment from 3.8 to 4.7 (`puppetserver-2.6.0-1` and `puppet-agent-1.7.0-1`), I'm seeing reports from the agents like the following: 2016-09-28 09:37:06 -0500 Puppet (warning): Unable to fetch my node definition, but the agent run will continue: 2016-09-28 09:37:06 -0500 Puppet (warning): Could not find terminus rest for indirection node 2016-09-28 09:37:06 -0500 /File[/var/lib/puppet/lib] (err): Failed to generate additional resources using 'eval_generate': Could not find terminus file for indirection file_metadata 2016-09-28 09:37:06 -0500 /File[/var/lib/puppet/lib] (err): Could not evaluate: Could not retrieve file metadata for puppet://host.domain.com/plugins: Could not find terminus rest for indirection file_metadata 2016-09-28 09:37:06 -0500 Puppet (err): Failed to apply catalog: Could not find terminus rest for indirection catalog Some background... - The puppetserver is running CentOS 7.2. - The Puppet agents are CentOS 6.8 and were upgraded using the `puppetlabs/puppet_agent` module via puppet. - The above warnings and errors are only produced when puppet-agent runs on it's schedule. Running it manually does not produce these warnings and errors. - We are also using `puppetlabs/tagmail` for email reporting. - I'm seeing these errors in both the tagmail and `/var/log/messages` on each agent node. Can anyone help me debug this?

Viewing all articles
Browse latest Browse all 6104

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>