Hi,
As per the subject, I'm seeing systemd-journald completely fail to start on a clean install, unless selinux is disabled, or at least toggled to permissive prior to journalds first startup. This would suggest to me that there's a policy issue stopping the initial startup creating/owning one or more files, but it's difficult to prove without the logging it provides.
Confirmed repeatable with the latest iso of OL-7.5 Server.x86_64. Is anyone else seeing this / aware of this issue?