RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

I ran into an issue when setting up systemd-journal-upload to "send" journal log entries to a remote host.  It appears that 

[root@vm2 CA]# grep User= /lib/systemd/system/systemd-journal-upload.service
User=systemd-journal-upload
DynamicUser=yes

[root@vm2 CA]# id systemd-journal-upload
id: ‘systemd-journal-upload’: no such user


Version-Release number of selected component (if applicable):
systemd-journal-remote-239-8.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1.  dnf install systemd-journal-remote
2.  id systemd-journal-upload

Actual results:
no user created.

Expected results:
since the service sets a user, I would expect the rpm to create it during install.

Additional info:

DynamicUser= creates the user dynamically at runtime and frees the allocation when the service finishes. The user is not added to /etc/passwd or similar and "id" command won't show it. For more information, see man systemd.exec(5), section CREDENTIALS.