Issue #7580 has been updated by Trevor Hemsley.
I am seeing this on 2.6.17 and it's the same as I remember it from the 0.24 days. I have done some investigation and it appears that puppet is always updating these fields every time it runs even though they are already the value that they should be. This causes problems in that every node that I have that has an ldap user definition now needs to have the ldapuser specified to allow it to update the directory and also, in an environment with replicated LDAP servers, every node that runs puppet will cause an update to ripple round the system. With > 60 systems and puppet running every 30 mins by default and making updates to, as far as I can see 3 fields per user, that's going to add quite a lot of overhead. I'm more concerned about having to have user credentials in puppet.conf on all my servers that allow puppet to update the centralised definitions in LDAP instead of locking that access down to just one or two. ---------------------------------------- Bug #7580: puppet always try to change user's gid on LDAP with same value. https://projects.puppetlabs.com/issues/7580#change-76777 Author: Satoru KURASHIKI Status: Accepted Priority: Normal Assignee: Category: LDAP Target version: Affected Puppet version: Keywords: Branch: I'm running puppet 2.6.7 on debian squeeze. Using ldap user provider, puppet always show messages like: notice: /resouce/path/to/user/gid: gid changed 'XX' to 'XX' It is no harm, but anyway needless behavior. # similar to #643? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
