Hi,
I notice that when I provision a host and puppet runs for the first time that it does not deliver all the change necessary for the next puppet run to be 'quiet'. In fact it can take several runs before the host is up-to-date. I have three concerns around this: 1. If I am spinning up a virtual host there may be a user requirement to start using it immediately - whereas it may take 90 minutes or more for puppet to complete (with 30 minute frequency of runs). 2. Is this behavior symptomatic of badly written puppet code? 3. I'm worried about a change that is partially delivered on a live system (post provisioning) - a host that is in a good state before and after a change may be in an unusable with part of the change applied. I'd like to know if there is a way that I can specify that a puppet run should iterate until all the available change has been applied? Or is there something I'm missing in my code to prevent this happening? Thanks in advance for any assistance. Regards, David PS, my environment is Satellite 6.0 and Puppet 3.6.2 -- 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/4b93f88a-5683-4a89-859b-9d5b29a19ed0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
