Issue #7442 has been updated by Josh Cooper. Category set to user Status changed from In Topic Branch Pending Review to Merged - Pending Release Target version set to 2.7.20 Affected Puppet version set to 2.6.2 Keywords set to solaris password max age Branch set to https://github.com/puppetlabs/puppet/pull/979
Merged in 2.7.x in <https://github.com/puppetlabs/puppet/commit/dea709e>. This has been this way since the feature was originally added in <https://github.com/puppetlabs/puppet/commit/0b4ce0898652268a772bfa1cb66cf67f41963d2b> for ticket #3046. ---------------------------------------- Bug #7442: User provided password age bug on Solaris with 2.7.0.rc2 https://projects.puppetlabs.com/issues/7442#change-68978 Author: Gary Law Status: Merged - Pending Release Priority: Normal Assignee: Category: user Target version: 2.7.20 Affected Puppet version: 2.6.2 Keywords: solaris password max age Branch: https://github.com/puppetlabs/puppet/pull/979 Hi Applying the following:- <pre> user { 'puppet': ensure => 'present', comment => 'Puppet', gid => '52', home => '/var/lib/puppet', password => '!!', password_max_age => '-1', password_min_age => '-1', shell => '/bin/true', uid => '52', } </pre> (known good on Darwin and CentOS) fails on Solaris: <pre> $ sudo puppet apply /etc/puppet/manifests/site.pp glaw@sv01:~ $ sudo puppet apply /etc/puppet/manifests/site.pp prtconf: devinfo facility not available err: /Stage[main]/Puppet/User[puppet]/password_min_age: change from to -1 failed: Could not set password_min_age on user[puppet]: Execution of '/usr/bin/passwd -n -1 puppet' returned 6: passwd: Invalid argument to option -n Invalid argument to option notice: /Stage[main]/Puppet/User[puppet]/password_max_age: password_max_age changed '' to '-1' notice: Class[Puppet]: Dependency User[puppet] has failures: true warning: Class[Puppet]: Skipping because of failed dependencies notice: Stage[main]: Dependency User[puppet] has failures: true warning: Stage[main]: Skipping because of failed dependencies notice: Finished catalog run in 0.13 seconds glaw@sv01:~ $ </pre> I *think* that the correct command for passwd in this case would be /usr/bin/passwd -x -1 puppet But in any event the provider doesn't seem to report on it, so even setting this correctly by hand doesn't cause puppet to apply the config without error: <pre> $ sudo puppet resource user puppet prtconf: devinfo facility not available user { 'puppet': ensure => 'present', comment => 'Puppet', gid => '52', home => '/var/lib/puppet', password => '!!', shell => '/bin/true', uid => '52', } </pre> Gary -- 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.
