Bug 2055576 - Openvswitch ipsec service failed to start: package files incorrectly refer to /usr/local/
Summary: Openvswitch ipsec service failed to start: package files incorrectly refer to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openvswitch
Version: 35
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Timothy Redaelli
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-17 09:48 UTC by bettswang
Modified: 2022-05-11 01:17 UTC (History)
7 users (show)

Fixed In Version: openvswitch-2.15.0-8.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-14 16:07:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
system message log (8.80 KB, text/plain)
2022-02-17 09:48 UTC, bettswang
no flags Details

Description bettswang 2022-02-17 09:48:08 UTC
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:

Comment 1 Ankur Sinha (FranciscoD) 2022-02-21 08:51:44 UTC
Bumping severity because it looks like the package is currently unusable because of this bug. Could a maintainer please take a look?

Comment 2 Timothy Redaelli 2022-03-25 17:58:18 UTC
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

Comment 3 Fedora Update System 2022-04-06 08:48:05 UTC
FEDORA-2022-6d8e4b5d34 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d8e4b5d34

Comment 4 Fedora Update System 2022-04-06 12:55:11 UTC
FEDORA-2022-870be5b681 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-870be5b681

Comment 5 Fedora Update System 2022-04-06 17:55:54 UTC
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.

Comment 6 Fedora Update System 2022-04-06 19:48:25 UTC
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.

Comment 7 Fedora Update System 2022-04-13 19:48:04 UTC
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.

Comment 8 Fedora Update System 2022-04-14 16:07:10 UTC
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.

Comment 9 Fedora Update System 2022-05-11 01:17:00 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.