Bug 1842067

Summary: systemd: Bad user or group name when it contains a dot
Product: [Fedora] Fedora Reporter: mark preston <mark>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 32CC: lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-245.6-2.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-05 02:29:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mark preston 2020-05-30 16:04:43 UTC 
Description of problem:
systemd: Bad user or group name "xxxx.yyyy", accepting for compatibility.
this is NOT a bad username and is valid. systemd should not dictate what is or isn't a valid username.

Version-Release number of selected component (if applicable):
systemd-245.4-1.fc32.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a user/group that has a dot in the name. e.g.  xxxx.yyyy
2. reboot the system
3. check messages for error

Actual results:
May 30 11:34:31 hostname systemd[270811]: Bad user or group name "xxxx.yyyy", accepting for compatibility.
May 30 11:34:31 hostname systemd[270811]: Bad user or group name "xxxx.yyyy", accepting for compatibility.
May 30 11:34:31 hostname systemd-userwork[270803]: Bad user or group name "xxxx.yyyy", accepting for compatibility.
May 30 11:34:31 hostname systemd-userwork[270803]: Bad user or group name "xxxx.yyyy", accepting for compatibility.


Expected results:
these errors should not be there

Additional info:
https://github.com/systemd/systemd/issues/12754
Comment 1 Zbigniew Jędrzejewski-Szmek 2020-05-31 10:56:25 UTC 
That message was changed in the latest version. Can you check if you still get the issue wiht
https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1?
Comment 2 mark preston 2020-05-31 16:29:57 UTC 
i installed the latest version and the message is gone as it should be.  I'll be adding +karma
Comment 3 Fedora Update System 2020-05-31 16:59:11 UTC 
FEDORA-2020-dd43dd05b1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1
Comment 4 Zbigniew Jędrzejewski-Szmek 2020-05-31 17:00:10 UTC 
Thanks for testing.
Comment 5 Fedora Update System 2020-06-01 03:12:34 UTC 
FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dd43dd05b1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2020-06-02 10:10:37 UTC 
FEDORA-2020-dd43dd05b1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1
Comment 7 Fedora Update System 2020-06-03 03:11:31 UTC 
FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dd43dd05b1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2020-06-05 02:29:31 UTC 
FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.