Bug 1832725
| Summary: | For 4.4 Beta - Openvswitch services fail to start. | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-distribution | Reporter: | lejeczek <peljasz> |
| Component: | openvswitch | Assignee: | Dominik Holler <dholler> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Dominik Holler <dholler> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | bugs, danken, dholler, michal.skrivanek |
| Target Milestone: | ovirt-4.4.1 | Flags: | sbonazzo:
ovirt-4.4?
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openvswitch2.11-2.11.0-50.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-08 08:26:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Domink, I think this will be fixed by your work on getting the FDP openvswitch stack rebuilt for CentOS right? (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? 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. we don't fully support centos stream just yet. i can't comment on the modifications, leaving that to dominik for consideration 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/ 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. |
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: