Bug 1832725 - For 4.4 Beta - Openvswitch services fail to start.
Summary: For 4.4 Beta - Openvswitch services fail to start.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: openvswitch
Version: 4.3.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.4.1
: ---
Assignee: Dominik Holler
QA Contact: Dominik Holler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-07 08:05 UTC by lejeczek
Modified: 2020-07-08 08:26 UTC (History)
4 users (show)

Fixed In Version: openvswitch2.11-2.11.0-50.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-08 08:26:34 UTC
oVirt Team: Network
Embargoed:
sbonazzo: ovirt-4.4?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1738896 0 unspecified CLOSED ovsdb-server.service fails with /var/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied) 2021-02-22 00:41:40 UTC

Description lejeczek 2020-05-07 08:05:01 UTC
Description of problem:

...
ovs|00002|daemon_unix|EMER|/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied)
Starting ovsdb-server ovsdb-server: /run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied)
[FAILED]
...

Fix I offer, which fixes the problem, is rather simple - get rid of redundant trickery from systemd service conf file and make it simple:

Type=forking
User=openvswitch
Group=hugetlbfs
Restart=on-failure
EnvironmentFile=/etc/openvswitch/default.conf
EnvironmentFile=-/etc/sysconfig/openvswitch
PIDFile=/run/openvswitch/ovsdb-server.pid
ExecStart=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd --no-monitor --system-id=random start $OPTIONS
ExecStop=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd stop
ExecReload=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd --no-monitor restart $OPTIONS
RuntimeDirectory=openvswitch
RuntimeDirectoryMode=0755

Same for ovs-vswitchd.service ??

And in - /etc/sysconfig/openvswitch - get rid of user/group definitions, instead with help of a comment say:

# If you want to use specific & different from default user & group then you must use custom systemd drop-in.


Ah..! And for the sake of consistency choose one /var/run VS /run
I suggest use:
...
%endif
  --with-pkidir=%{_sharedstatedir}/openvswitch/pki \
  --with-rundir=%{_rundir}/openvswitch

...
in .spec file.

Version-Release number of selected component (if applicable):

4.4 Beta
openvswitch-2.11.1-5.el8.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Sandro Bonazzola 2020-05-07 16:19:01 UTC
Domink, I think this will be fixed by your work on getting the FDP openvswitch stack rebuilt for CentOS right?

Comment 2 Dominik Holler 2020-05-07 18:54:39 UTC
(In reply to Sandro Bonazzola from comment #1)
> Domink, I think this will be fixed by your work on getting the FDP
> openvswitch stack rebuilt for CentOS right?

Yes.
openvswitch-2.11.1-5.el8.x86_64 is not compatible to CentOS > 8.1.


On which CentOS version did this issue occur?

Comment 3 lejeczek 2020-05-07 20:02:08 UTC
Hi. What do you mean by 'not compatible'? I'm using/running this version right now (with the fix I proposed) on Centos 8 Stream.

Comment 4 Michal Skrivanek 2020-05-11 12:46:24 UTC
we don't fully support centos stream just yet.

i can't comment on the modifications, leaving that to dominik for consideration

Comment 5 Dominik Holler 2020-06-22 08:46:53 UTC
Open vSwitch works on CentOS 8.2 with the official repos, even with oVirt 4.4.0 .
See 
https://gerrit.ovirt.org/#/c/109724/
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OJANYWGYNIXTXOLE2EKSJ3PNPUV6EG5Z/

Comment 6 Sandro Bonazzola 2020-07-08 08:26:34 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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