I agree, I learnt my lesson, but thankfully, it was in my testing environment - I've been writing shitty basic puppet code, and I'd just built a new puppet master, which was behaving very odd! That's when I noticed it was V3 - Good job I don;t run updates in my master - It also hit me that I don't actually manage the puppet client versions - I think I'm going to have to add that to my default node definition.
On 3 October 2012 17:38, Jeffrey Watts <jeffrey.w.wa...@gmail.com> wrote: > This update will serve to educate them that using ensure => latest for > critical packages like this in a production environment is not a good idea. > :) > > Jeffrey. > > > On Wed, Oct 3, 2012 at 9:36 AM, Mister Guru <misteritg...@gmail.com>wrote: > >> I'm sending this email to start this thread, feel free to comment as >> appropriate. I'm going to assume that it's going to take a while for most >> people to actually realise that the puppet update may be giving them some >> issues, so, comments and suggestion please! >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
