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:

The /etc/systemd/journal-{remote,upload}.conf files (an the services) point to default paths that do not seem to exist on my test hosts:

# ls -ld /etc/ssl/private/
ls: cannot access '/etc/ssl/private/': No such file or directory


# ls -ld /etc/ssl/ca
ls: cannot access '/etc/ssl/ca': No such file or directory

These are defined as the locations like this:

# cat /etc/systemd/journal-remote.conf 
[Remote]
# Seal=false
# SplitMode=host
# ServerKeyFile=/etc/ssl/private/journal-remote.pem
# ServerCertificateFile=/etc/ssl/certs/journal-remote.pem
# TrustedCertificateFile=/etc/ssl/ca/trusted.pem

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

How reproducible:
always

Steps to Reproduce:
1.  dnf -y install systemd-journal-remote
2.  if you try to install keys into the default locations, you must create the missing dirs.


Actual results:
dirs do not exist

Expected results:
dirs already exist or systemd-journal-remote points to new standard locations that do exist?

Additional info:
Or is this maybe a documentation issue?

They are just examples. You can put the certificates wherever you like and then, of course, you have to adjust the configuration.