Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10900

Puppet gid attribute in user resource always applying changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 6.21.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Agent OS:
      CentOS 7
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      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.

      Desired Behavior:

      Puppet will not attempt to change the gid if this is already set to the correct value.

      Actual Behavior:

      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)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              cnambrutis Caleb Ambrutis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support