I try to learn ovs ipsec on the fedora. And installed step by step under under the direction of ovs offical manual , return a error “FileNotFoundError: [Errno 2] No such file or directory: ‘/usr/local/share/openvswitch/vswitch.ovsschema’”.
It seems that fedora build python3-openvswitch rpm package which define a wrong path to find ovs. Because the ovs installed by dnf is in the path /usr/share/openvswitch , not int the path /usr/local/.
Remember that the official manual is a guideline, intended for most cases, and not an absolute. Each distro is able to make certain changes, and since fedora does not use /usr/local the same as debian and ubuntu but instead uses /usr/share for most of that you will have to make exceptions as to the guide paths.
Fedora has several ovs and ipsec packages that may be installed and could make thing easier for you instead of focusing on the details of installation and instead focus on the usage.
Those packages may be installed by using sudo dnf install \*ovs\* \*ipsec\*. The list of packages to be installed may be more than you want, so peruse it and pick what you feel will help you the most.
AS your said , I did the command “dnf install python3-openvswitch libreswan openvswitch openvswitch-ipsec”. But the problem is that the system return me a error when I want to start the openvswitch-ipsec.service. The error message is “[Errno 2] No such file or directory: ‘/usr/local/share/openvswitch/vswitch.ovsschema’”.
So i submit this issue to openvswitch-issue, they remind me that fedora package seems broken.
Here are their answer:
Looking at the dirs.py file in the python3-openvswitch package, it contains /usr/local/... paths and this is obviously incorrect, because the rest of OVS built without the local prefix. Please, report that to fedora.
Yes, that sounds correct.Packages in Fedora should not be using or pointing to /usr/local/. Can you please file a bug against the package so that the maintainer can fix this? (reporting it here to the forum does not mean a bug has been filed or that the maintainer has been made aware of it in any other way)
It depends on the maintainer—we’re all volunteers that work on Fedora packages and tasks in our free time after we take care of our dayjobs and personal lives. So it can vary depending on how busy the maintainer is.
I’ve bumped the severity of the bug, so hopefully they’ll get to it soon. It’s only been a couple of days though, and these days were the weekend, so hopefully they’ll get to it this work week.
FEDORA-2022-6d8e4b5d34 has been pushed to the Fedora 35 testing repository.
Soon you’ll be able to install the update with the following command: sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6d8e4b5d34
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d8e4b5d34