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:
With version 239-73.el8 of systemd, the boot.iso and also any machine updated to this version of systemd has this error when booting:

A start job is running for 'Flush Journal to Persistent Storage'

After 90 Seconds, it fails and the boot continues.

Version-Release number of selected component (if applicable):

systemd-239-73.el8.x86_64

How reproducible:

Always

(I tested this on the CI system , 2 new VM installs and one cold iron machine.  Both new installs and updates, even the ISOs to run the installer have this issue.  I did not test arches other than x86_64)  

Steps to Reproduce:
1.  Install a new (or update an existing) CentOS Stream 8 system to systemd-239-73.el8.

Additional info:

I am currently NOT releasing this compose to the CentOS Mirrors (unless instructed to do so) as this will break every install of CentOS Stream 8 that upgrades.

This package can be accessed in koji:

https://kojihub.stream.centos.org/koji/buildinfo?buildID=30931

Or tested from:

https://composes.stream.centos.org/stream-8/production/CentOS-Stream-8-20230327.0/

systemd-239-71.el8 does not exhibit this issue.

NOTE: This version (systemd-239-73.el8) was already released in a previous compose.  I only noticed it when testing the new secureboot kernel.  This issue actually passes our CI testing.  So, this is already live and on the mirrors.

*** This bug has been marked as a duplicate of bug 2174645 ***