On Wednesday, July 30, 2014 7:31:38 AM UTC-5, Jason Antman wrote: > > I've seen those environments. I've worked in them. A few host types in my > current environment are like that. IT IS A BUG. The only valid reason for > this is either a bug in your manifests/modules, or that things aren't > ordered properly. > >
You misunderstand me. I can readily believe that some environments *do* take multiple Puppet runs to converge. I'm saying that there is nothing in those environments that inherently prevents Puppet from syncing the whole system in just one run. So, agreed, if systems take multiple Puppet runs to converge to a stable configuration then there is a bug in the manifest set, data, and/or ENC. > That being said... don't run via cron. > ... if all you want it for is provisioning. For Puppet's core use -- ongoing configuration management -- there are a lot of advantages to scheduling agent runs via cron instead of running the agent as a daemon. Also a couple of limitations. 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/eaaf4e5f-9346-4356-b85a-3d8cbc8ae5af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
