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.

Bug 1706740

Summary: SELinux prevents dbus-daemon sending messages
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Heger <jheger>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED DUPLICATE QA Contact: Milos Malik <mmalik>
Severity: low Docs Contact:
Priority: low    
Version: 7.6CC: kvolny, lvrabec, mmalik, plautrba, ssekidde, vmojzis, zpytela
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 08:10:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Heger 2019-05-06 08:19:17 UTC
Description of problem:
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31
selinux-policy-3.13.1-244.el7.noarch
----
time->Sat May  4 06:51:10 2019
type=USER_AVC msg=audit(1556967070.155:653): pid=1286 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied  { send_msg } for msgtype=method_return dest=:1.39 spid=2939 tpid=2938 scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:system_r:sosreport_t:s0-s0:c0.c1023 tclass=dbus  exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'


Link to log: http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/05/35137/3513718/6820506/92147735/423272535/avc.log

Link to task: https://beaker.engineering.redhat.com/recipes/6820506#task92147735

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-244.el7.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Karel Volný 2019-06-03 10:35:57 UTC
is this fixed?

- no fail with selinux-policy-3.13.1-246.el7.noarch here https://tcms.engineering.redhat.com/run/360112/#caserun_21249549

Comment 3 Lukas Vrabec 2019-06-03 11:54:04 UTC
Hi Karel, 

It's not fixed in SELinux policy, but if you're not able to reproduce it, let's close this BZ. Do you agree? 

Thanks,
Lukas.

Comment 4 Karel Volný 2019-06-04 08:10:38 UTC
looks like I have found the source of the randomness ... it appears to be wrongly assigned message, error generated by the previous test

the test that causes this is /CoreOS/abrt/Regression/Upstream

see https://beaker.engineering.redhat.com/jobs/3583693

and it is reported already as bug 1705599

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