-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.0.beta
-
None
-
frr-9.1-3.el10
-
None
-
Moderate
-
rhel-sst-cs-net-perf-services
-
ssg_core_services
-
16
-
1
-
False
-
-
None
-
None
-
Pass
-
Automated
-
None
Lots of SELinux failures, but the central ones seem to be:
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file watchfrr.vty.
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file zserv.api.
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file zebra.vty.
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file mgmtd_fe.sock.
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file ripd.vty.
Apr 04 21:09:46 cash setroubleshoot[1910]: SELinux is preventing watchfrr from create access on the sock_file staticd.vty.
Reproducible: Always
Steps to Reproduce:
1.Fully update Fedora 40 and reboot
2.Try to start frr
3.There is no step 3
Note: This prevents FRR from starting properly. This is caused by a change in the selinux-policy here: https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/commit/6dd5c78a955daec7bff449e963b0b95720d05084. All files in /var/lock now need to be in /run/lock and all files in /var/run/ need to go to /run/
- links to
-
RHSA-2024:130900 frr update