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.
These two additional commits need to be backported:
commit 676fdceecce7f6e31c7ffdd9ecebb579fb7e4fb6 (HEAD -> rawhide, upstream/rawhide)
Author: Zdenek Pytela <zpytela>
Date: Thu Feb 24 12:29:52 2022 +0100
Allow systemd-logind dbus chat with sosreport
commit 05e940f535497768c2b4a8c37365b5b5156eda75
Author: Zdenek Pytela <zpytela>
Date: Fri Feb 25 14:16:52 2022 +0100
Allow chronyd send a message to sosreport over datagram socket
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 (selinux-policy bug fix and enhancement 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/RHBA-2022:1995
Looks like only a half of the communication was allowed: # sesearch -A -s abrt_t -t sosreport_t -c dbus -p send_msg # sesearch -A -s timedatex_t -t sosreport_t -c dbus -p send_msg # sesearch -A -s chronyd_t -t sosreport_t -c unix_dgram_socket -p sendto # sesearch -A -s chronyd_t -t sosreport_t -c unix_dgram_socket # sesearch -A -s sosreport_t -t abrt_t -c dbus -p send_msg allow dbusd_unconfined nsswitch_domain:dbus send_msg; allow dbusd_unconfined system_bus_type:dbus send_msg; # sesearch -A -s sosreport_t -t timedatex_t -c dbus -p send_msg allow dbusd_unconfined timedatex_t:dbus send_msg; # sesearch -A -s sosreport_t -t chronyd_t -c unix_dgram_socket -p sendto allow unconfined_domain_type domain:unix_dgram_socket { accept append bind connect create getattr getopt ioctl listen lock map name_bind read recv_msg recvfrom relabelfrom relabelto send_msg sendto setattr setopt shutdown write };