Ask Your Question

How do I tell puppet apply to always store the freshest facts in PuppetDB?

asked 2013-04-23 17:26:15 -0600

Christian Berg gravatar image

We're running a masterless Puppet setup where puppet apply is run regularly (via MCollective) on a large-ish number of nodes. We want to use PuppetDB for exported resources, as a queryable inventory and report store.

With our initial configuration, the facts for a new node were collected from facter and stored in the PuppetDB during the first run of puppet apply. Subsequent runs would take the stale facts stored in the PuppetDB, however.

As suggested in the (PuppetDB documentation), we created a routes.yaml file with the following content ... (more)

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2013-05-09 07:07:08 -0600

updated 2013-08-15 10:27:07 -0600

The configuration you have supplied in your routes.yaml file actually disables fact integration with PuppetDB entirely, this is not by accident however as it's working around a known bug:


This bug caused Fact storage for PuppetDB when using puppet apply to not work correctly. This has been fixed now in release 1.4.x, and documentation on how to configure this is available here:

Basically if you adjust your routes.yaml file to something like what we have below, fact ... (more)

edit flag offensive delete link more


That sounds great, thanks for the fix! We'll upgrade and try this out as soon as we can.

Christian Berg gravatar imageChristian Berg ( 2013-08-15 10:56:37 -0600 )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


Asked: 2013-04-23 17:26:15 -0600

Seen: 1,083 times

Last updated: Aug 15 '13