Last modified: 2013-06-15 19:56:20 UTC
Starting from a fresh instance, I tried to have puppet add a new system user 'pp' using this definition: user { "pp": name => "pp", home => "/opt/pp", comment => "pediapress system user", shell => "/bin/bash", ensure => "present", gid => "mwlib", allowdupe => false, system => true, managehome => true, } The outcome was a user with uid 999, which conflicted with an ldap (assumed, not confirmed) user. drwxr-xr-x 2 grunny mwlib 4096 2012-03-19 15:52 pp On Mark's suggestion I switched the manifest to use the systemuser class instead: systemuser { "pp": name => "pp", home => "/opt/pp", shell => "/bin/bash" } This created a non-system user with UID 2191. The standard user range does not appear to conflict with LDAP so with our broken systemuser class we would not have seen an issue before. Mark fixed systemuser to system=>true in production, but we need to fix labs host UID range configuration before importing that fix to the test repo.
(In reply to comment #0) > Mark fixed systemuser to system=>true in production, but we need to fix labs > host UID range configuration before importing that fix to the test repo. Obviously the test branch part is wrong because that branch is not used any more. (at all, by anyone) Production currently has system => true. FIXED ?
is this still a problem? this bug is open for several months
Jeff Green can you please confirm this needs a fix? otherwise I am closing this...
This bug is related to something what is not being used anymore, and nobody else seems to have this problem