Bug 2042873

Summary: selinux broken
Product: [Fedora] Fedora Reporter: 319513897
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 35CC: dwalsh, grepl.miroslav, lvrabec, mmalik, omosnace, pkoncity, plautrba, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-20 16:10:14 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 319513897 2022-01-20 09:53:51 UTC 
Today I upgrade my system like yesterday, but I use kde-discover. However, after I reboot my system, I get many warnings come from podman, this warnings I had solved through whistle module. So I check whether I had that.

I use `semodule -l | grep whistl` to check it, it obviously I have it. Then I try uninstall whistle module and reinstall it. 

Then:

# semodule -r whistle
libsemanage.semanage_direct_remove_key: Removing last whistle module (no other whistle module exists at another priority).
Problems processing filecon rules
Failed post db handling
Post process failed
semodule:  Failed!

I try relabel system to fix this, but it useless.

For convince, I had disable selinux already. Please fix this as much as quickly.
Comment 1 319513897 2022-01-20 10:04:46 UTC 
When I reinstall container-selinux, then some error happend:

  reinstall: container-selinux-2:2.170.0-2.fc35.noarch                                                  
  run scripts: container-selinux-2:2.170.0-2.fc35.noarch                                                     
Problems processing filecon rules
Failed post db handling
Post process failed
/usr/sbin/semodule:  Failed!
/etc/selinux/targeted/contexts/files/file_contexts:  invalid context system_u:object_r:container_var_lib_t:s0


It seems this bug come from container-selinux
Comment 2 Zdenek Pytela 2022-01-20 16:10:14 UTC 
Please update to selinux-policy-35.11-1.fc35

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