Description of problem: SELinux is preventing ebtables from 'read' accesses on the Datei ebtables.lock. ***** Plugin catchall (100. confidence) suggests ************************** Wenn Sie denken, dass es ebtables standardmäßig erlaubt sein sollte, read Zugriff auf ebtables.lock file zu erhalten. Then sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Do zugriff jetzt erlauben, indem Sie die nachfolgenden Befehle ausführen: # ausearch -c 'ebtables' --raw | audit2allow -M my-ebtables # semodule -X 300 -i my-ebtables.pp Additional Information: Source Context system_u:system_r:firewalld_t:s0 Target Context system_u:object_r:virt_var_run_t:s0 Target Objects ebtables.lock [ file ] Source ebtables Source Path ebtables Port <Unbekannt> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-3.14.6-36.fc33.noarch Local Policy RPM selinux-policy-targeted-3.14.6-36.fc33.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.11.16-200.fc33.x86_64 #1 SMP Wed Apr 21 16:08:37 UTC 2021 x86_64 x86_64 Alert Count 1 First Seen 2021-05-02 10:56:58 CEST Last Seen 2021-05-02 10:56:58 CEST Local ID a4522010-34c0-40a1-931d-84ccac001bf8 Raw Audit Messages type=AVC msg=audit(1619945818.632:510): avc: denied { read } for pid=11179 comm="ebtables" name="ebtables.lock" dev="tmpfs" ino=1853 scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u:object_r:virt_var_run_t:s0 tclass=file permissive=0 Hash: ebtables,firewalld_t,virt_var_run_t,file,read Version-Release number of selected component: selinux-policy-targeted-3.14.6-36.fc33.noarch Additional info: component: selinux-policy reporter: libreport-2.14.0 hashmarkername: setroubleshoot kernel: 5.11.16-200.fc33.x86_64 type: libreport Potential duplicate: bug 1747939
Hi, The file in the setroubleshoot report has incorrect label. The path was not logged, but in the likely case it is /run, you can fix the label with # /sbin/restorecon -v /run/ebtables.lock This change, however, does not persist boot. Are you aware how the lockfile was created?
I have simple start the firewalld service after removing the iptables/ip6ables service. An then the message was shown.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.