Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
PUP 4.9.3
-
Tested with multiple Windows versions (i.e. Server 2012R2) and Puppet Apply 4.9.3
-
Windows
-
Windows Kanban
-
Customer Feedback
-
Normal
-
2 - 5-25% of Customers
-
3 - Serious
-
5 - $$$$$$
-
Group is one of the core resource types and should work as expected on all supported platform including windows.
-
Bug Fix
-
-
Needs Assessment
Description
After leaving a Domain Windows systems may still contain not resolvable domain accounts inside local groups, i.e. in Administrators group:
When trying to manage this group using auth_membership => true (to ensure all not resolvable domain user accounts are tidied to only have the local user Administrator inside the local Administrators group), Puppet will fail:
group {'Administrators': |
members => ['Administrator'], |
auth_membership => true |
}
|
Tested with the following Puppet Apply command:
puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }
|
Error: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784
|
Error: /Stage[main]/Main/Group[Administrators]/members: change from TEST-WIN2012\Administrator,S-1-5-21-776561741-1409082233-725345543-15784 to TEST-WIN2012\Administrator failed: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784
|
Attachments
Issue Links
- relates to
-
PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
-
- Closed
-
-
PUP-4208 Name Collision When Managing Users or Groups in Trusted Domains
-
- Closed
-
-
PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
-
- Closed
-