Issue #5273 has been reported by Rene van der Linden.
----------------------------------------
Bug #5273: password_max_age in user type is reported as absent while it's not
https://projects.puppetlabs.com/issues/5273
Author: Rene van der Linden
Status: Unreviewed
Priority: Normal
Assignee:
Category: user
Target version: 2.6.3
Affected Puppet version: 2.6.3rc2
Keywords: user type password_max_age
Branch:
@user {
"appl1":
ensure => present,
uid => "300",
gid => "300",
comment => "Functional user",
home => "/home/appl1",
password_max_age => "99999",
shell => "/bin/bash",
managehome => "true";
}
The password_max_age does get properly changed by puppet, and even the OS
(CentOS 5.5 / RHEL5.5) reports the user settings correct, puppet does want to
change it again and again as it can't seem to retrieve the settings and thinks
it's unset
notice: /Stage[main]/User::Virtual/User[appl1]/password_max_age: is absent,
should be 99999 (noop)
notice: Finished catalog run in 0.14 seconds
When the OS is queried, it report the correct value for max_age
# chage -l appl1
...
Maximum number of days between password change : 99999
NOTE: ruby shadow 1.4.1-7 is installed
--
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.
