[Expired for puppet (Ubuntu) because there has been no activity for 60
days.]
** Changed in: puppet (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768864
It was just working under 16.04 and 17.10.
And: How could it make sense and be an intended upstream change if
puppet reports and confirms changes that it does not perform?
(I will test this soon.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
So could that just have changed over the years upstream?
And if so can you now run your config against e.g. a Cloud image which has this
use created on first boot and still succeed with a config that dropped
allowdupe?
--
You received this bug notification because you are a member of Ubuntu
Bug
(it's not the regular ubuntu distribution, but images like lxc, lxd,
docker, raspberry that come with a preset user ubuntu with uid 1000,
which was one of the reasons to add allowdupe => true, and to remove
accounts like ubuntu in a later step. it was furthermore required if
older accounts exist an
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,
This is strange.
Using a separate class with just such a single user resource, it works.
In a huge puppet setup with hundreds of resources (that was working
under 14.04, 16.04, 16.10,17.04.17.10) it does not work.
I will do some debugging and try to find the reason for that.
--
You received thi
# id puppet
uid=112(puppet) gid=119(puppet) groups=119(puppet)
$ puppet resource -e user danisch
user { 'danisch':
ensure => present,
uid=> '1015',
gid=> '119',
comment=> 'Hadmut Danisch',
shell => '/bin/bash',
home => '/home/danisch'
}
When saving
