Issue #11675 has been updated by Nicolas Di Gregorio.
Oliver Hookins wrote: > I can confirm the same behaviour on 2.7.9. From my brief skimming of the code > it appears that the useradd provider has no mechanism to query the existing > account expiry date (I guess technically it should be done through the Shadow > library?) and hence it has no option but to set the expiry on every run. > > Seems like the solution is to add adequate queries to verify the current > state of the user. > > [...] I've the same issue with 3.0.1 ---------------------------------------- Bug #11675: user expiry option fills up the logs https://projects.puppetlabs.com/issues/11675#change-73099 Author: Bill Tong Status: Accepted Priority: Normal Assignee: Category: provider Target version: Affected Puppet version: 2.7.9 Keywords: Branch: puppet should not change the expiry for a user unless the requested expiry differs from the current expiry. user { "root": uid => 0, ensure => "present", "expiry" => "2015-01-01", } will *always* log every time puppet runs. -- 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.
