Bug 1593770 - ovs-vswitchd and ovsdb-server crash after logrotate runs
Summary: ovs-vswitchd and ovsdb-server crash after logrotate runs
Keywords:
Status: CLOSED DUPLICATE of bug 1589836
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Open vSwitch development team
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-21 14:39 UTC by Andrew Austin
Modified: 2018-06-21 14:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-21 14:43:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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