Bug 1881204

Summary: SELinux is preventing abrt-action-sav from 'write' accesses on the file rpmdb.sqlite-wal.
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: antonio.montagnani, dwalsh, grepl.miroslav, lvrabec, mike, mmalik, plautrba, rgodinez, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:53b69c22b90dfec56a10860d72a15336c0bd135bd2be140760c745f80e100ee3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-23 05:32:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ankur Sinha (FranciscoD) 2020-09-21 19:33:53 UTC
Description of problem:
Fresh update to F33, seeing this on logging in.
SELinux is preventing abrt-action-sav from 'write' accesses on the file rpmdb.sqlite-wal.

*****  Plugin catchall_labels (83.8 confidence) suggests   *******************

If you want to allow abrt-action-sav to have write access on the rpmdb.sqlite-wal file
Then you need to change the label on rpmdb.sqlite-wal
Do
# semanage fcontext -a -t FILE_TYPE 'rpmdb.sqlite-wal'
where FILE_TYPE is one of the following: abrt_etc_t, abrt_tmp_t, abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_log_t, abrt_var_run_t, afs_cache_t, initrc_tmp_t, kdump_crash_t, mail_home_rw_t, mock_var_lib_t, postfix_postdrop_t, puppet_tmp_t, rhsmcertd_var_run_t, rpm_log_t, rpm_var_cache_t, rpm_var_run_t, sysfs_t, user_cron_spool_t, user_tmp_t, usr_t.
Then execute:
restorecon -v 'rpmdb.sqlite-wal'


*****  Plugin catchall (17.1 confidence) suggests   **************************

If you believe that abrt-action-sav should be allowed write access on the rpmdb.sqlite-wal 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 'abrt-action-sav' --raw | audit2allow -M my-abrtactionsav
# semodule -X 300 -i my-abrtactionsav.pp

Additional Information:
Source Context                system_u:system_r:abrt_t:s0-s0:c0.c1023
Target Context                system_u:object_r:var_lib_t:s0
Target Objects                rpmdb.sqlite-wal [ file ]
Source                        abrt-action-sav
Source Path                   abrt-action-sav
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            <Unknown>
Local Policy RPM              selinux-policy-targeted-3.14.6-27.fc33.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.8.10-300.fc33.x86_64 #1 SMP Thu
                              Sep 17 18:20:53 UTC 2020 x86_64 x86_64
Alert Count                   14
First Seen                    2020-09-21 20:31:54 BST
Last Seen                     2020-09-21 20:31:57 BST
Local ID                      35ea73f0-14ea-4ae3-b5a0-72d1c438901e

Raw Audit Messages
type=AVC msg=audit(1600716717.115:654): avc:  denied  { write } for  pid=26360 comm="abrt-action-lis" name="rpmdb.sqlite-wal" dev="sdb5" ino=1858348 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_lib_t:s0 tclass=file permissive=0


Hash: abrt-action-sav,abrt_t,var_lib_t,file,write


Additional info:
component:      selinux-policy
reporter:       libreport-2.14.0
hashmarkername: setroubleshoot
kernel:         5.8.10-300.fc33.x86_64
type:           libreport

Potential duplicate: bug 1540366

Comment 1 Zdenek Pytela 2020-09-23 05:32:58 UTC

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

Comment 2 antonio montagnani 2020-10-30 05:18:51 UTC
*** Bug 1893087 has been marked as a duplicate of this bug. ***

Comment 3 Rafael Godínez Pérez 2020-11-02 16:09:51 UTC
*** Bug 1893796 has been marked as a duplicate of this bug. ***

Comment 4 Michael Shinn 2020-11-06 18:43:23 UTC
*** Bug 1895484 has been marked as a duplicate of this bug. ***