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

Bug 1593770

Summary:	ovs-vswitchd and ovsdb-server crash after logrotate runs
Product:	Red Hat OpenStack	Reporter:	Andrew Austin <aaustin>
Component:	openvswitch	Assignee:	Open vSwitch development team <ovs-team>
Status:	CLOSED DUPLICATE	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	aaustin, apevec, chrisw, rhos-maint, srevivo
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:	2018-06-21 14:43:17 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 Andrew Austin 2018-06-21 14:39:49 UTC

Description of problem:
When running an OSP13 cloud with OVN networking, it appears that ovs-vswitchd and ovsdb-server are crashing on all overcloud nodes following log rotation.

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

How reproducible:
Deploy an OSP13 overcloud with OVN networking. Wait overnight and note that ovs-vswitchd has crashed on all overcloud nodes.

Actual results:
ovs-vswitchd and ovsdb-server are dead on all overcloud nodes and traffic is not flowing.

Expected results:
We rotate logs without breaking the data plane.

Additional info:

The connection with logrotate is assumed from the logs below. The same log pattern appears on all nodes at different times.

Jun 21 03:00:56 dal-osp1-compute-1 logrotate-crond: kill -HUP 1250
Jun 21 03:00:56 dal-osp1-compute-1 logrotate-crond: kill -HUP 1354
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00045|reconnect|INFO|unix:/run/openvswitch/db.sock: connection closed by peer
Jun 21 03:00:56 dal-osp1-compute-1 ovs-ctl: ovsdb-server is not running.
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00046|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connection closed by peer
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00047|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connection closed by peer
Jun 21 03:00:56 dal-osp1-compute-1 ovs-ctl: ovs-vswitchd is not running.
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00048|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting...
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00049|rconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: connection failed (No such file or directory)
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00050|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: waiting 2 seconds before reconnect
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00051|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting...
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00052|rconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: connection failed (No such file or directory)
Jun 21 03:00:56 dal-osp1-compute-1 journal: 2018-06-21T07:00:56Z|00053|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: waiting 2 seconds before reconnect

Comment 1 Andrew Austin 2018-06-21 14:43:17 UTC

Someone brought BZ1589836 to my attention. This appears to be the same issue.

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