Jira (PUP-10896) Puppet users with forcelocal are no longer idempotent

Title: Message Title

Trey Dockendorf created an issue

Puppet Version: 7.4.0 and 6.21.0
Puppet Server Version: Masterless to demonstrate issue
OS Name/Version: CentOS 7

Defining a `forcelocal` user results in Puppet constantly anting to change the GID for the user.

Desired Behavior:

Idempotent apply of forcelocal user.

Actual Behavior:

[root@23aff6d4a202 /]# cat user-group.pp

user { 'keycloak':

  ensure     => 'present',

  name       => 'keycloak',

  forcelocal => true,

  shell      => '/sbin/nologin',

  gid        => 'keycloak',

  uid        => undef,

  home       => '/var/lib/keycloak',

  managehome => true,

  system     => true,

group { 'keycloak':

  ensure     => 'present',

  name       => 'keycloak',

  forcelocal => true,

  gid        => undef,

  system     => true,

[root@23aff6d4a202 /]# puppet apply user-group.pp

Notice: Compiled catalog for 23aff6d4a202 in environment production in 0.01 seconds

Notice: /Stage[main]/Main/Group[keycloak]/ensure: created

Notice: /Stage[main]/Main/User[keycloak]/ensure: created

Notice: Applied catalog in 0.04 seconds

[root@23aff6d4a202 /]# puppet apply user-group.pp

Notice: Compiled catalog for 23aff6d4a202 in environment production in 0.01 seconds

Notice: /Stage[main]/Main/User[keycloak]/gid: gid changed '13' to 'keycloak'

Notice: Applied catalog in 0.02 seconds

I am fairly certain the issue resides in this change: https://tickets.puppetlabs.com/browse/PUP-10857

This message was sent by Atlassian Jira

--
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 [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386956.1612964187000.138224.1612964220058%40Atlassian.JIRA.

Reply via email to