That is up to you. You said you were not sure if your actions were really implemented. Thus I showed you the places (files) where you can find what is the present situation. If that is in line with what you wanted and did can only you know.
But to recap what was found:
user aleksey (UID=1000) is configured with primary group aleksey (GID=1000);
user aleksey is also a member of group users (GID=100).
If you have other users where you want to know what their primary group is and of which other groups they are also a member, you now know how to check that.
You can also look direct in /etc/groupto see what groups exist and what users are added to them.
You can also look in /etc/passwd to see what the primary group of each user is.
Something different is of course still the error you got. We did not tackle that until now.
I am only explaining to the OP what he has and how he can “see” what he has.
What you show might be the default on new installations. I doubt that on a long time existing Tumbleweed installation an upgrade will complete overthrow the existing user/group configuration.
But I do not use TW, thus you may enlighten me.
@hcvv Since your not using Tumbleweed, please be careful when offering advice at a system level if you don’t understand the changes are being/have made.
It is really unclear what you mean here or what you did. When you want any comment, then SHOW the relevant entries in /etc/passwd and /etc/group.
And also do not forget that when you change the primary group of a user, you should also change the group ownership of all his files (most of them, when not all will be in /home/aleksey and also /home/aleksey itself must be changed).
It is also unclear why you are doing these things. Remember that it is better to explain what your goal is then just telling us that a particular step is acting unexpected.