Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1741398

Summary:	[OVS2.11] OVS daemon failed to start under 8.1.0
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Jean-Tsung Hsiao <jhsiao>
Component:	openvswitch2.11	Assignee:	David Marchand <dmarchan>
Status:	CLOSED DUPLICATE	QA Contact:	ovs-qe
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	FDP 19.E	CC:	ctrautma, dmarchan, jhsiao, kzhang, ralongi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 09:12:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jean-Tsung Hsiao 2019-08-15 03:15:08 UTC

Description of problem: [OVS2.11] OVS daemon failed to start under 8.1.0

[root@netqe7 ~]# systemctl stop openvswitch
[root@netqe7 ~]# systemctl start openvswitch
A dependency job for openvswitch.service failed. See 'journalctl -xe' for details.
[root@netqe7 ~]# journalctl -xe -l
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com ovs-ctl[4496]: not removing bridge module because bridges exist (virbr0) ... (warnin>
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Control process exited, code=exited status=1
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Failed with result 'exit-code'.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: Failed to start Open vSwitch Forwarding Unit.
-- Subject: Unit ovs-vswitchd.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit ovs-vswitchd.service has failed.
-- 
-- The result is RESULT.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Service RestartSec=100ms expired, scheduling resta>
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Automatic restarting of the unit ovs-vswitchd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: Stopped Open vSwitch Forwarding Unit.
-- Subject: Unit ovs-vswitchd.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit ovs-vswitchd.service has finished shutting down.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Start request repeated too quickly.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: ovs-vswitchd.service: Failed with result 'exit-code'.
Aug 14 23:04:45 netqe7.knqe.lab.eng.bos.redhat.com systemd[1]: Failed to start Open vSwitch Forwarding Unit.
-- Subject: Unit ovs-vswitchd.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit ovs-vswitchd.service has failed.
-- 
-- The result is RESULT.
[root@netqe7 ~]# rpm -q openvswitch2.11
openvswitch2.11-2.11.0-18.el8fdp.x86_64
[root@netqe7 ~]# uname -r
4.18.0-128.el8.x86_64
[root@netqe7 ~]# 



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

[root@netqe7 ~]# rpm -q openvswitch2.11
openvswitch2.11-2.11.0-18.el8fdp.x86_64
[root@netqe7 ~]# uname -r
4.18.0-128.el8.x86_64

How reproducible: Reproducible


Steps to Reproduce:
1. Start OVS2.11
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 David Marchand 2019-08-15 06:00:15 UTC

I suspect it is related to bz1711739.

- Do you have no pci device bound to vfio-pci?
- Does setting the ovs-vsctl --no-wait set Open_vSwitch .  other_config:dpdk-extra='--iova-mode=va' parameter resolve the issue?

Comment 2 Jean-Tsung Hsiao 2019-08-15 09:54:36 UTC

(In reply to David Marchand from comment #1)
> I suspect it is related to bz1711739.
> 
> - Do you have no pci device bound to vfio-pci?
> - Does setting the ovs-vsctl --no-wait set Open_vSwitch . 
> other_config:dpdk-extra='--iova-mode=va' parameter resolve the issue?


This is a totally different issue from bz1711739. In this case ovs-vswitchd failed to come up --- no /var/log/openvswitch/ovs-vswitchd.log. It happened with or without ixgbe bound to vfio-pci. Please check the "journalctl -xe -l" log above.

In bz1711739 case the daemon always come up with log file showing memory issue.

Will send you login info in case you want to login to take a look.

Comment 3 David Marchand 2019-08-19 09:12:53 UTC

Looked at your system logs, the ovs scripts can't read /lib/modules and can't load the openvswitch kmod.
I upgraded to openvswitch-selinux-extra-policy-1.0-18.el8fdp.noarch and it fixes the issue.

*** This bug has been marked as a duplicate of bug 1732647 ***