Affects Version/s: PUP 6.21.0
Fix Version/s: None
Template:PUP Bug Template customfield_10700 387190
Agent OS:CentOS 7
Method Found:Needs Assessment
QA Risk Assessment:Needs Assessment
Puppet Version: 6.21.0
Puppet Server Version: Foreman 2.1.4
OS Name/Version: CentOS 6 and CentOS 7
Starting with Puppet version 6.21.0, when applying a manifest with the gid attribute set to a specific group using the user resource, puppet will always apply the group ID to the user account even when it is set correctly. In Foreman, reports will show puppet is applying modules on every run, which affects our internal reporting. This occurs when using the puppet agent and puppet apply a basic manifest or command that sets the gid of a user account. It appears as puppet is reading the group ID as a string value instead of a numeric value.
Puppet will not attempt to change the gid if this is already set to the correct value.
Puppet attempts to change the gid even if this is set correctly.
Example: when running with puppet agent --test --trace --debug (snippet):
Debug: Executing: '/sbin/lusermod -g 1001 testuser'
Notice: /Stage[main]/Test/User[testuser]/gid: gid changed '1001' to 1001 (corrective)