Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
Open vSwitch domain was not allowed to access certain files in the openvswitch_var_run_t domain
Consequence:
Open vSwitch would fail to initialize DPDK software infrastructure without selinux enabled.
Fix:
Allow openvswitch_t to access openvswitch_var_run_t domain.
Result:
Open vSwitch can now start the DPDK infrastructure.
(In reply to Aaron Conole from comment #3)
> Please let me know if this fixes the issue. If so, I'll update the policies.
Yes, that fixes the issue.
Thanks!
Jean
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:2437
Description of problem: [OVS] Got an AVC when configuring an OVS-dpdk bridge type=AVC msg=audit(1530189404.974:291): avc: denied { map } for pid=13871 comm="ovs-vswitchd" path="/run/openvswitch/.rte_config" dev="tmpfs" ino=72769 scontext=system_u:system_r:openvswitch_t:s0 tcontext=system_u:object_r:openvswitch_var_run_t:s0 tclass=file permissive=0 NOTE: Same issue happened under Rhel-8.0 Alpha. Version-Release number of selected component (if applicable): [root@netqe17 jhsiao]# uname -a Linux netqe17.knqe.lab.eng.bos.redhat.com 3.10.0-915.el7.x86_64 #1 SMP Fri Jun 22 23:49:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@netqe17 jhsiao]# rpm -qa | grep selinux selinux-policy-targeted-3.13.1-204.el7.noarch openvswitch-selinux-extra-policy-1.0-3.el7fdp.noarch libselinux-utils-2.5-13.el7.x86_64 libselinux-python-2.5-13.el7.x86_64 libselinux-2.5-13.el7.x86_64 selinux-policy-3.13.1-204.el7.noarch [root@netqe17 jhsiao]# How reproducible: Reproducible Steps to Reproduce: 1. Provision a server with Rhel-7.6 2. Config a OVS-dpdk bridge; Below is the reproducer. [root@netqe17 jhsiao]# cat /home/jhsiao/ovs_dpdk_no_nic.sh ovs-vsctl set Open_vSwitch . other_config={} ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x0004 ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="4096,4096" ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true ovs-vsctl --if-exists del-br ovsbr0 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x4040 ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev 3. Actual results: Expected results: Additional info: