Bug 1300839 - SELinux is preventing python3 from 'write' accesses on the directory /var/cache/yum.
Summary: SELinux is preventing python3 from 'write' accesses on the directory /var/cac...
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman   
(Show other bugs)
Version: 24
Hardware: x86_64 Unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:07bf32ac44ae251df25b769a7ee...
Depends On:
TreeView+ depends on / blocked
Reported: 2016-01-21 21:58 UTC by Giulio 'juliuxpigface'
Modified: 2017-08-08 12:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-08 12:41:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Giulio 'juliuxpigface' 2016-01-21 21:58:48 UTC
Description of problem:
I encountered this after the boot of a Cinnamon Live session (Rawhide 20160121 Cinnamon Spin)
SELinux is preventing python3 from 'write' accesses on the directory /var/cache/yum.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that python3 should be allowed write access on the yum directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep python3 /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:blueman_t:s0
Target Context                system_u:object_r:rpm_var_cache_t:s0
Target Objects                /var/cache/yum [ dir ]
Source                        python3
Source Path                   python3
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-168.fc24.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.5.0-0.rc0.git7.1.fc24.x86_64 #1
                              SMP Wed Jan 20 18:34:53 UTC 2016 x86_64 x86_64
Alert Count                   4
First Seen                    2016-01-21 16:44:45 EST
Last Seen                     2016-01-21 16:44:46 EST
Local ID                      2a4b6b3c-8cbf-483b-b787-5b02cbfc5288

Raw Audit Messages
type=AVC msg=audit(1453412686.283:539): avc:  denied  { write } for  pid=2286 comm="blueman-mechani" name="/" dev="tmpfs" ino=19895 scontext=system_u:system_r:blueman_t:s0 tcontext=system_u:object_r:rpm_var_cache_t:s0 tclass=dir permissive=0

Hash: python3,blueman_t,rpm_var_cache_t,dir,write

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.6.3
hashmarkername: setroubleshoot
kernel:         4.5.0-0.rc0.git7.1.fc24.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2016-01-25 07:36:57 UTC
It looks like something what we could dontaudit.

Comment 2 Jan Kurik 2016-02-24 14:19:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

Comment 3 Fedora Admin XMLRPC Client 2016-06-21 16:27:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2016-06-21 20:07:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora End Of Life 2017-07-25 19:49:38 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-08-08 12:41:31 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.