Introduction
It occurs a number of times a day that changes on the Puppetmaster are not recognized immediately by the Puppet agents. If this is the case Puppet needs to be run more than 5 times (e.g. X<5min) before the changes are recognized.
- Puppet version: 3.7.3
- X>100 Puppet-agent nodes
- One Puppetmaster
Expected
Changes on Puppetmaster should be recognized by Puppet-agent immediately always
Attempts
One of the attempts to solve the issue was executed after reading this documentation:
Puppet includes a basic puppet master web server based on Ruby’s WEBrick library.
(This is what Puppet uses if you run puppet master on the command line or use
most puppetmaster init scripts.)
You cannot use this default server for real-life loads, as it can’t handle
concurrent connections; it is only suitable for small tests with ten nodes
or fewer. You must configure a production quality web server before you
start managing your nodes with Puppet.
Any Rack-based application server stack will work with a puppet master, but if
you don’t have any particular preference, you should use Passenger combined
with Apache. This guide shows how to configure Puppet with this software.
- Run puppetmaster using Passenger.
- Another attempt was to stop the automatic run of puppet on Puppet-agent nodes every 30 minutes
Current
The attempts did not solve the issue, i.e. changes on the Puppetmaster are not immediately recognized by the Puppet-agent