Found the problem. Or came closer to it.
That's the part from the puppet class for user setup:
user{
$name:
ensure => present,
groups => $groups,
shell => $shellpath,
password => $password,
gid => $groupname,
uid => $uid,
comment => $description,
allowdupe => true, # Distributionen kommen oft mit eigenem
Benutzer
require => $shelldep;
}
This issues log messages about success, but doesn't do anything. But it works
when removing the allowdupe parameter.
allowdupe was set because otherwise a standard setup which comes with
the user ubuntu with uid 1000 oder if older accounts exist, they would
block creating new users. This way new users are created, possibly with
same uids as existing users (such as ubuntu with 1000), which are
cleaned up in a later step to avoid having no valid user at all.
For testing purposes I've created a class which just consists of
class tests::versuch {
user { 'danisch':
ensure => present,
comment => 'Hadmut Danisch',
shell => '/usr/bin/zsh',
allowdupe => true,
}
}
and call
usermod danisch -s /bin/bash ; puppet apply -e 'include tests::versuch'
to see whether it changes the passwd entry. It works without allowdupe, but
doesn't work with allowdupe (i.e. issues positive log messages, but doesn't
save them.
It was working until ubuntu 17.10.
regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768864
Title:
puppet ressources user and group not doing anything
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1768864/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
