Jira (PUP-8223) User and group modifications should respect forcelocal

[Trey Dockendorf (JIRA)]

Title: Message Title

Trey Dockendorf created an issue   Puppet / PUP-8223 User and group modifications should respect forcelocal Issue Type: Improvement Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2017/12/03 11:38 AM Environment: RHEL 6 and 7 Priority: Normal Reporter: Trey Dockendorf The user and group resources do not use local commands when modifying a user or group. This can result in failure to make changes to locally added user or groups if that user or group already exists in LDAP. Example error: 2017-11-21 09:19:49 -0500 Puppet (err): Could not set gid on group[munge]: Execution of '/usr/sbin/groupmod -g 73 munge' returned 4: groupmod: GID '73' already exists 2017-11-21 09:19:49 -0500 /Stage[main]/Munge::User/Group[munge]/gid (err): change from 486 to 73 failed: Could not set gid on group[munge]: Execution of '/usr/sbin/groupmod -g 73 munge' returned 4: groupmod: GID '73' already exists Using lgroupmod on this particular system was only way to allow Puppet to continue to function. lgroupmod -g 73 munge This issue presented itself when Puppet was told to set munge UID/GID after the package had already auto-created the user/group with different UID/GID. The module that adds the user/group uses forcelocal=>true https://github.com/treydock/puppet-munge/blob/master/manifests/user.pp I propose that both user and group resources respect forcelocal for all types of operations. Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.