Bug 2177131

Summary: SELinux is preventing metadata-provid from 'write' accesses on the file ContactDataMigrate.orx.
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: dwalsh, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1bbad2449c44d0637027e1e96d14c73a4ba7f8c89d84fab8312bd0bcee48bc77;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Mikhail 2023-03-10 06:18:18 UTC
Description of problem:
This happens when I start podman container with binded host directories.
SELinux is preventing metadata-provid from 'write' accesses on the file ContactDataMigrate.orx.

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

If you believe that metadata-provid should be allowed write access on the ContactDataMigrate.orx 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 'metadata-provid' --raw | audit2allow -M my-metadataprovid
# semodule -X 300 -i my-metadataprovid.pp

Additional Information:
Source Context                system_u:system_r:container_t:s0:c48,c687
Target Context                unconfined_u:object_r:user_home_t:s0
Target Objects                ContactDataMigrate.orx [ file ]
Source                        metadata-provid
Source Path                   metadata-provid
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.8-1.fc39.noarch
Local Policy RPM              selinux-policy-targeted-38.8-1.fc39.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 6.3.0-
                              0.rc1.20230309git6a98c9cae232.18.fc39.x86_64+debug
                              #1 SMP PREEMPT_DYNAMIC Thu Mar 9 23:54:03 +05 2023
                              x86_64
Alert Count                   1
First Seen                    2023-03-10 11:13:22 +05
Last Seen                     2023-03-10 11:13:22 +05
Local ID                      a13d8206-4247-45c9-964c-393511ad89ba

Raw Audit Messages
type=AVC msg=audit(1678428802.973:413): avc:  denied  { write } for  pid=61968 comm="metadata-provid" name="ContactDataMigrate.orx" dev="nvme1n1" ino=750708 scontext=system_u:system_r:container_t:s0:c48,c687 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1


Hash: metadata-provid,container_t,user_home_t,file,write

Version-Release number of selected component:
selinux-policy-targeted-38.8-1.fc39.noarch

Additional info:
reporter:       libreport-2.17.8
reason:         SELinux is preventing metadata-provid from 'write' accesses on the file ContactDataMigrate.orx.
package:        selinux-policy-targeted-38.8-1.fc39.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.3.0-0.rc1.20230309git6a98c9cae232.18.fc39.x86_64+debug
comment:        This happens when I start podman container with binded host directories.
component:      selinux-policy

Comment 1 Mikhail 2023-03-10 06:18:20 UTC
Created attachment 1949472 [details]
File: description

Comment 2 Mikhail 2023-03-10 06:18:22 UTC
Created attachment 1949473 [details]
File: os_info

Comment 3 Fedora Release Engineering 2023-08-16 07:11:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.