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: After update to RHEL 7.3 systemd becomes unuseable and the only workaround we found was reinstall of 7.1 (possibly 7.2).

It manifested on our db servers running ScyllaDB.

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

How reproducible:
Very, happens both after update to 7.3 and on fresh install.

Steps to Reproduce:
1. Install 7.3
2. Install ScyllaDB 1.4 (or 1.3)
3. Enable scylladb using systemctl

Actual results:
systemd becomes unusable and even restart requires force.

Expected results:
A working db installed as in 7.1 where it worked just fine.

Additional info:
https://github.com/scylladb/scylla/issues/1846
https://github.com/systemd/systemd/issues/2632

Both are connected but may or may not contain the entire story.
We are locked to 7.1 until systemd works again.
The patch above seems at least crucial but perhaps not enough.

The exact same problem has already been reported by one of our customers. We're working on it.

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

I cannot see the referenced issue. Is there any eta for it?

It's a regular RHEL-7.3 bug, which means that ETA is likely RHEL-7.4.

Ok thx.