Created attachment 1861646 [details] system message log Created attachment 1861646 [details] system message log Created attachment 1861646 [details] system message log Description of problem: I had installed openvswitch step by step under the ovs offical manual on the fedora32-35. But the openvswitch-ipsec.service was unabled to start. I had alread checked with ovs devs, they said "py file in the python3-openvswitch package contains /usr/local/... paths and this is obviously incorrect, because the rest of OVS built without the local prefix" Version-Release number of selected component (if applicable): libreswan.x86_64_4.6-1.fc35 openvswitch.x86_64_2.15.0-7.fc35 openvswitch-ipsec.x86_64_2.15.0-7.fc35 python3-openvswitch.x86_64_2.15.0-7.fc35 How reproducible: install the related ovs package , disable the selinux, add the ipsec service to firewall. Then start the ipsec service. Steps to Reproduce: 1.dnf install python3-openvswitch libreswan openvswitch openvswitch-ipsec 2.systemctl start firewalld;firewall-cmd --add-service ipsec 3.systemctl start openvswitch-ipsec.service Actual results: [root@fedora ~]# systemctl start openvswitch-ipsec.service Job for openvswitch-ipsec.service failed because the control process exited with error code. See "systemctl status openvswitch-ipsec.service" and "journalctl -xeu openvswitch-ipsec.service" for details. Expected results: service could start successlly Additional info:
Bumping severity because it looks like the package is currently unusable because of this bug. Could a maintainer please take a look?
Reported upstream at https://mail.openvswitch.org/pipermail/ovs-dev/2022-March/392764.html, but I'll fix it on spec file by deleting dirs.py since the fix requires a tarball respin from upstream
FEDORA-2022-6d8e4b5d34 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d8e4b5d34
FEDORA-2022-870be5b681 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-870be5b681
FEDORA-2022-870be5b681 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-870be5b681` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-870be5b681 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
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 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6d8e4b5d34 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-870be5b681 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.