Details
-
Type:
Bug
-
Status: Needs Information
-
Priority:
Normal
-
Resolution: Unresolved
-
Affects Version/s: PUP 3.6.2, PUP 3.7.5
-
Fix Version/s: None
-
Component/s: Types and Providers
-
Labels:
-
Environment:
Solaris 11.2
-
Template:customfield_10700 95185
-
Team:Night's Watch
Description
This is the class that I use to test role creation on a Solaris 11.2
class users {
|
user { 'testrole':
|
ensure => 'role',
|
gid => '10',
|
managehome => 'true',
|
password => '$5$A860FWa1$jWGKgl2Y39/ciuKv8DO6nd27u9hh.DlUGpKgrvE1ujD',
|
password_max_age => '-1',
|
uid => '1001'
|
}
|
}
|
After I apply this manifest the /etc/shadow file contains
testrole:UP:::::::
When I reapply for the second time the manifest then the password is set.
But if the password_min_age and/or password_max_age attributes are used I receive the Folowing error:
Notice: /Stage[main]/Users::User[testrole]/password: changed password
|
Error: No command role_password defined for provider
|
Error: /Stage[main]/Users/User[testrole]/password_min_age: change from -1 to 0 failed: No command role_password defined for provider
|
Error: No command role_password defined for provider
|
Error: /Stage[main]/Users/User[testrole]/password_max_age: change from -1 to 99999 failed: No command role_password defined for provider
|