Tom, That is definitely a reasonable concern and thanks for finding it! I'll write up a JIRA ticket for this and we'll see if we can get it fixed in a reasonable time frame.
Thanks, Bryan Jen On Friday, November 20, 2015 at 9:32:22 AM UTC-7, Tom Limoncelli wrote: > > We recently upgraded to the latest puppetlabs-concat module. The new > module generated the exact same files as before which was great (yea > upwards compatibility!) but because a new concatfragments.rb file was > installed, puppet triggered downstream "reloads" and reloaded our > server (boo! undesired reloads!). As a result, our keepalived's were > reloaded and that caused unplanned failovers between replicas. > > The good news is that we caught this in testing so it didn't affect > production. However, our workaround was ugly. We paused puppet agent, > manually updated concatfragments.rb, then unpaused puppet agent. > > Is it possible for the module to deploy updates to concatfragments.rb > without it being considered trigger-worthy? > > Thanks, > Tom > > -- > Email: [email protected] <javascript:> Work: > [email protected] > Skype: YesThatTom > Blog: http://EverythingSysadmin.com > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/00efe1a6-a99c-4645-888b-055f7210a290%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
