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

Puppet assumes gid of user needs to be corrected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 6.21.0
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Agent OS:
      Ubuntu 16.04 (i386, amd64)
    • Master OS:
      CentOS 7
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 6.21.0
      Puppet Server Version: 6.15.1
      OS Name/Version: Centos 7 / ubuntu 20.04

      Desired Behavior:

      Do not correct users if not needed

      Actual Behavior:

       

      Each puppet run I get the message 

      Notice: /Stage[main]/Sbt::Users/User[oswaldk]/gid: gid changed '100' to 'users' (corrective)

      This user's gid is 100 which is the users group.

      For every user we manage we get this message on each puppet run. The user resource has the forcelocal parameter set as true.

      We get this message since the 6.21 update. Puppet agent 6.20 did not do this.

      Apparently this changed in 6.21:

      https://puppet.com/docs/puppet/6.21/release_notes_puppet.html#release_notes_puppet_x-19-0

      The puppet resource for user oswaldk:

      user

      { oswaldk:   ensure => present,   home => '/home/oswaldk',     uid => '2000',   comment => 'Oswald Knoppers',   password => 'xxx',   managehome => true,   forcelocal => true,   gid => 'users',   shell => '/bin/bash',   groups => 'ssh_users',   require => Group['ssh_users'], }

      It looks like this problem was introduced with version 6.21

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oswald Oswald Knoppers
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support