Jira (PUP-10303) Windows user management fails if group contains not resolvable Domain accounts

0 views
Skip to first unread message

Shaun McEvoy (JIRA)

unread,
Feb 20, 2020, 12:55:12 PM2/20/20
to puppe...@googlegroups.com
Shaun McEvoy created an issue
 
Puppet / Bug PUP-10303
Windows user management fails if group contains not resolvable Domain accounts
Issue Type: Bug Bug
Assignee: Unassigned
Created: 2020/02/20 9:54 AM
Priority: Critical Critical
Reporter: Shaun McEvoy

Puppet Version:6.11.1, 6.12, 6.13
Puppet Server Version: 6.7.1
OS Name/Version: Windows Server 2012 R2

Unable to manage windows users if a not resolvable SID exists in a group.  Also, the command 'puppet resource group' fails if there is a not resolvable SID in any group on the server.  We currently run Puppet 5.5.6 and this is not an issue.  We are holding off on upgrading.  

Steps to reproduce:

  1. **Create a test user in Active Directory
  2. Add the test user to the local Administrators group on a windows server
  3. Delete the test user in Active Directory
  4. There are two tests
    1. Run puppet resource group command
    2. Run puppet apply -e "group {'Administrators': ensure => 'present', members => ['Administrator'], auth_membership => false }" 

Desired Behavior:

Puppet should ignore not resolvable SIDs so we can still manage windows users locally

Actual Behavior:

 

After running 'puppet resource group':  Error: Could not run: Could not resolve name: S-1-5-21-994416979-1451695006-1560425512-1327 (unresolvable)

After running puppet apply -e "group {'Administrators': ensure => 'present', members => ['Administrator'], auth_membership => false }":  Error: /Stage[main]/Main/Group[Administrators]: Could not evaluate: Could not resolve name: S-1-5-21-994416979-1451695006-1560425512-1327 (unresolvable)

 

 

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Josh Cooper (JIRA)

unread,
Feb 20, 2020, 2:44:10 PM2/20/20
to puppe...@googlegroups.com

Mihai Buzgau (JIRA)

unread,
Feb 25, 2020, 11:03:04 AM2/25/20
to puppe...@googlegroups.com

Mihai Buzgau (Jira)

unread,
Mar 5, 2020, 4:44:03 AM3/5/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: PR NW - Triage 2020-03-17
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Mihai Buzgau (Jira)

unread,
Mar 5, 2020, 4:44:03 AM3/5/20
to puppe...@googlegroups.com

Ciprian Badescu (Jira)

unread,
Mar 12, 2020, 11:18:04 AM3/12/20
to puppe...@googlegroups.com

Mihai Buzgau (Jira)

unread,
Mar 18, 2020, 4:54:04 AM3/18/20
to puppe...@googlegroups.com

Mihai Buzgau (Jira)

unread,
Apr 1, 2020, 3:51:03 AM4/1/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: NW - 2020-03-17, NW - 2020-04-01 , NW - 2020-04-15

Ciprian Badescu (Jira)

unread,
Apr 1, 2020, 5:43:03 AM4/1/20
to puppe...@googlegroups.com

Ciprian Badescu (Jira)

unread,
Apr 1, 2020, 5:46:02 AM4/1/20
to puppe...@googlegroups.com
Ciprian Badescu updated an issue
Change By: Ciprian Badescu
Release Notes Summary: Before this fix, if an Active Directory user was added as member of a local group and the user was deleted afterwards, puppet cannot manage the respective group members anymore.
With this fix, puppet will me able to manage the group by showing SID instead of account name for non-resolvable users

Gabriel Nagy (Jira)

unread,
Apr 23, 2020, 8:03:02 AM4/23/20
to puppe...@googlegroups.com
Gabriel Nagy updated an issue
Change By: Gabriel Nagy
Fix Version/s: PUP 6.15.0
Fix Version/s: PUP 5.5.20

Claire Cadman (Jira)

unread,
Apr 27, 2020, 8:30:03 AM4/27/20
to puppe...@googlegroups.com

zendesk.jira (Jira)

unread,
Nov 10, 2020, 3:18:03 AM11/10/20
to puppe...@googlegroups.com
zendesk.jira updated an issue
Change By: zendesk.jira
Zendesk Ticket Count: 1
Zendesk Ticket IDs: 41900

zendesk.jira (Jira)

unread,
Nov 10, 2020, 3:18:04 AM11/10/20
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages