Puppet

Replying to [ticket:569 luke]:

puppetd now checks to see if facts have changed, and if they have, it recompiles without checking if the server-side configuration has changed.

This works fine in theory, except that Facter now includes multiple dynamic facts, including information about memory and swap, which are always going to change. This means that for those platforms that support these facts, the configuration will get recompiled every time.

It isn’t clear to me that this is a defect vs an enhancement request. Dynamic facts might actual kick off an actual change in a configuration (e.g., if memory utilization crosses a certain threshold, then I don’t want the ‘super-sized’ version of ‘big-fat-memory-hog’ to run; instead, I want the ‘diet-right’ version of ‘slim-and-trim’ to run instead). Being able to specify this type of difference is a feature enhancement, I suspect.

In the meantime, you could add a ‘ignore dynamic facts’ flag or some such and specifically list the properties that would not kick off a recompile (e.g., ‘—ignore-dynamic-facts=memory,swap’).

This hasn’t been used since we disabled staleness checking for catalogs, which was early in the 0.24 release cycle.

This does need to get resurrected as we bring back long-term catalog retention, but it should probably be a new ticket.