Puppet users - Nov 2010 - User type password_max_age not working

I have a virtual user (mqm) in puppet (v2.6.2 on CentOS 5.5 with Ruby
1.8.6.383-6)

@user {
      "mqm":
              ensure           => present,
              uid              => "300",
              gid              => "300",
              comment          => "Functional user",
              home             => "/home/mqm",
              password_max_age => "99999",
              shell            => "/bin/bash",
              managehome       => "true";
} # End user

and it does get created on the server when I realze it, but each time
I run puppet again, it reports the max_age is not set

notice: /Stage[main]/User::Virtual/User[mqm]/password_max_age: is
absent, should be 99999 (noop)
notice: Finished catalog run in 0.14 seconds

but this is not true as the system reports the user to created
correctly

# chage -l mqm
Last password change                                    : Nov 11, 2010
Password expires                                        : never
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 99999
Number of days of warning before password expires       : 7

NOTE: I have also tried the latest versions of puppet (2.6.3-0.3.rc2),
but no change.

please help

Regards,
Rene



-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

rvlinden <rene.vanderlinden73@gmail.com> writes:
> I have a virtual user (mqm) in puppet (v2.6.2 on CentOS 5.5 with Ruby
> 1.8.6.383-6)
[...]
> and it does get created on the server when I realze it, but each time
> I run puppet again, it reports the max_age is not set
>
> notice: /Stage[main]/User::Virtual/User[mqm]/password_max_age: is
> absent, should be 99999 (noop)
> notice: Finished catalog run in 0.14 seconds
[...]
> please help
Mmmm.  It looks to me like the adduser provider requires the Ruby
''shadow''
library to be able to get the "age" field - or it unconditionally
returns
"absent" without any additional information.

Which would explain your problem.  Can you verify my guess, please?

1. Install the ruby shadow library, confirm if the problem goes away.
2. If so, file a bug complaining that isn''t entirely reasonable.
   (At least, not silently. :)

    http://projects.puppetlabs.com/projects/puppet

Regards,
        Daniel

-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Ruby shadow 1.4.1-7 was already installed so it has to be something
else

I will report it as a bug

On Nov 11, 11:26 pm, Daniel Pittman <dan...@rimspace.net>
wrote:
> rvlinden <rene.vanderlinde...@gmail.com> writes:
> > I have a virtual user (mqm) in puppet (v2.6.2 on CentOS 5.5 with Ruby
> > 1.8.6.383-6)
>
> [...]
>
> > and it does get created on the server when I realze it, but each time
> > I run puppet again, it reports the max_age is not set
>
> > notice: /Stage[main]/User::Virtual/User[mqm]/password_max_age: is
> > absent, should be 99999 (noop)
> > notice: Finished catalog run in 0.14 seconds
>
> [...]
>
> > please help
>
> Mmmm.  It looks to me like the adduser provider requires the Ruby
''shadow''
> library to be able to get the "age" field - or it unconditionally
returns
> "absent" without any additional information.
>
> Which would explain your problem.  Can you verify my guess, please?
>
> 1. Install the ruby shadow library, confirm if the problem goes away.
> 2. If so, file a bug complaining that isn''t entirely reasonable.
>    (At least, not silently. :)
>
>    http://projects.puppetlabs.com/projects/puppet
>
> Regards,
>         Daniel
>
> --
> ✣ Daniel Pittman            ✉ dan...@rimspace.net            ☎ +61 401 155
707
>                ♽ made with 100 percent post-consumer electrons
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.