On Sunday, December 6, 2015 at 8:27:21 AM UTC-6, César wrote:
>
> Hi all,
>
> we're seeing every now and then an odd behaviour with Puppet catalog
> compilation. Basically, we modify and save the node manifests and a few
> seconds later we trigger a catalog run to apply the changes.
> However, what we see is that sometimes the Puppet master compiles the old
> version of the node manifest, leaving changes behind and requiring two
> catalog runs to apply all of them.
>
> A sample site.pp would look like this:
>
>
> import "/path/to/manifests/plugins/ms1.pp"
>
> import "/path/to/manifests/plugins/n1.pp"
>
> import "/path/to/manifests/plugins/n2.pp"
>
> node default {}
>
>
> I would like to know if using import might be causing this? (We use Puppet
> 3.3.2)
> If that's not the case, do you have any hints or tips to troubleshoot the
> issue? How does the Puppetmaster handle the compilation of the node
> manifest? We tried to use the configuration option to avoid caching, but so
> far that didn't fix it.
>
>
Are you sure the master is running Puppet 3.3? What you're describing
sounds like an effect of new-style environment caching, but I don't think
that was implemented yet in Puppet 3.3. (The Puppet version on the agents
doesn't matter for this purpose.)
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/b30626d2-8c22-4505-92e9-995ade55779a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
