Closed cfasnacht closed 2 months ago
I think this behavior might be because of the handling of the group member with uid
=0. An XML diff results in this:
199a200,215
> <group>
> <name>admins</name>
> <description>System Administrators</description>
> <scope>system</scope>
> <gid>1999</gid>
> <member>0</member>
> <priv>page-all</priv>
> </group>
> <user>
> <name>root</name>
> <descr>System Administrator</descr>
> <scope>system</scope>
> <groupname>admins</groupname>
> <password></password>
> <uid>0</uid>
> </user>
265,292d280
< <group>
< <name>admins</name>
< <description>System Administrators</description>
< <scope>system</scope>
< <priv>page-all</priv>
< <gid>1999</gid>
< <member/>
< </group>
< <user>
< <name>root</name>
< <password></password>
< <scope>system</scope>
< <descr>[ ANSIBLE ]</descr>
< <ipsecpsk/>
< <otp_seed/>
< <shell>/sbin/nologin</shell>
< <uid>0</uid>
< <full_name>[ ANSIBLE ]</full_name>
< <expires/>
< <authorizedkeys/>
< <apikeys>
< <item>
< <key>XW+sfiAV5bpfHekR4t7OAOaWtYE4eADgHYHKPQKdfxeSHFjh0M6fRVmMfILZSG6avVpLRMlMgTdb7ciS</key>
< <secret>$6$$eQrsnn4atGr.8N8G.HHCKktddJQwBsdfgOf9qNfCH.P2Ki2gvM05kJXmzGlOEYwXnYJwvjSn5iteNQmzszu30j.</secret>
< </item>
< </apikeys>
< <groupname>admins</groupname>
< </user>
Since we have always tested this module with vagrant boxes, where we used the user vagrant
with some other uid
we have not yet encountered this case.
We need to test and fix those cases where uid could have some special values like 0
and potentially even 1
.
This breaks all users:
Output: