Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 customer is getting this error message when rebooting:
systemd: Failed to propagate agent release message: Transport endpoint is not connected

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

How reproducible:


Steps to Reproduce:
1. Reboot the system
2.
3.

Actual results:
Spurious error messages

Expected results:
No error messages

Additional info:
This appears to be a race condition when shutting down the system dbus. Systemd is still trying to send messages to the dbus while at the same time shutting it down.
This issue has already been reported to upstream and fixed in v235:
https://github.com/systemd/systemd/issues/6777
commit https://github.com/systemd/systemd/pull/6780/commits/d5f1532657da107f1c8be8a97c15d964cd96665c

All right, let's downgrade the log message to "debug" as upstream did.

PR: https://github.com/systemd-rhel/rhel-7/pull/61

fix merged to github master branch -> https://github.com/systemd-rhel/rhel-7/pull/61

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: systemd security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4007