Bug 1400580

Summary: SELinux is preventing /usr/lib/systemd/systemd-bootchart from 'create' accesses on the file /run/log/.
Product: [Fedora] Fedora Reporter: W Agtail <crash70>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: crash70, dominick.grift, dwalsh, lvrabec, plautrba, ssekidde
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:7e9b5c2d60fb4a8b23e4c85ecf0bc7dd125f777a67a8bd13da92b5608060e0f9;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:58:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description W Agtail 2016-12-01 14:19:36 UTC
Description of problem:
bootchart.service reports SELinux alert during system boot process.
SELinux is preventing /usr/lib/systemd/systemd-bootchart from 'create' accesses on the file /run/log/.

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

If you believe that systemd-bootchart should be allowed create access on the  file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-bootcha' --raw | audit2allow -M my-systemdbootcha
# semodule -X 300 -i my-systemdbootcha.pp

Additional Information:
Source Context                system_u:system_r:init_t:s0
Target Context                system_u:object_r:syslogd_var_run_t:s0
Target Objects                /run/log/ [ file ]
Source                        systemd-bootcha
Source Path                   /usr/lib/systemd/systemd-bootchart
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           systemd-bootchart-231-2.fc25.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-224.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.8.10-300.fc25.x86_64 #1 SMP Mon
                              Nov 21 18:59:16 UTC 2016 x86_64 x86_64
Alert Count                   2
First Seen                    2016-12-01 12:58:16 GMT
Last Seen                     2016-12-01 14:11:54 GMT
Local ID                      84664177-a5fd-4678-a5b6-d9db2036e5df

Raw Audit Messages
type=AVC msg=audit(1480601514.282:114): avc:  denied  { create } for  pid=773 comm="systemd-bootcha" name="bootchart-20161201-1411.svg" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:syslogd_var_run_t:s0 tclass=file permissive=0


type=SYSCALL msg=audit(1480601514.282:114): arch=x86_64 syscall=open success=no exit=EACCES a0=7ffe9447a5e0 a1=80241 a2=1b6 a3=1 items=1 ppid=1 pid=773 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-bootcha exe=/usr/lib/systemd/systemd-bootchart subj=system_u:system_r:init_t:s0 key=(null)

type=CWD msg=audit(1480601514.282:114): cwd=/

type=PATH msg=audit(1480601514.282:114): item=0 name=/run/log/ inode=11577 dev=00:16 mode=040755 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:syslogd_var_run_t:s0 nametype=PARENT

Hash: systemd-bootcha,init_t,syslogd_var_run_t,file,create

Version-Release number of selected component:
selinux-policy-3.13.1-224.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.10-300.fc25.x86_64
type:           libreport

Comment 1 Fedora End Of Life 2017-11-16 18:42:08 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 2 Fedora End Of Life 2017-12-12 10:05:18 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
bug.

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

Comment 3 W Agtail 2018-01-25 18:46:48 UTC
Same issue with rawhide 28
Many thanks.

Comment 4 Fedora End Of Life 2018-02-20 15:24:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 5 Ben Cotton 2019-05-02 19:37:27 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 Ben Cotton 2019-05-28 23:58:32 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
bug.

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