Bug 1636234

Summary:	[3.9] Upgrading control plane from 3.7.44 to 3.7.54 occasionally causes ovsdb-server.service start operation to timeout, also affects 3.9
Product:	OpenShift Container Platform	Reporter:	Patrick Dillon <padillon>
Component:	Cluster Version Operator	Assignee:	Patrick Dillon <padillon>
Status:	CLOSED ERRATA	QA Contact:	Meng Bo <bmeng>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, bbennett, cdc, cscribne, emahoney, jiajliu, jokerman, knakayam, mmccomas, mmichels, sdodson, weliang, zzhao
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: systemd has default service timeout of 90 seconds and in some cases ovsdb-server does not start up in that time. Consequence: openvswitch, which has a dependency on ovsdb-server, cannot start and installation fails. Fix: increase systemd timeout for ovsdb-server to five minutes. Result: ovsdb-server does not timeout and openvswitch starts successfully.	Story Points:	---
Clone Of:	1616440	Environment:
Last Closed:	2018-12-13 19:27:05 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:
Bug Depends On:	1616440
Bug Blocks:

Comment 1 Patrick Dillon 2018-10-04 20:24:00 UTC

PR: https://github.com/openshift/openshift-ansible/pull/10324

Comment 2 Scott Dodson 2018-10-08 14:11:46 UTC

Pr merged.

Comment 3 Scott Dodson 2018-10-16 13:49:54 UTC

In openshift-ansible-3.9.47-1

Comment 4 zhaozhanqi 2018-10-24 01:46:23 UTC

Verified this bug on openshift-ansible-3.9.48-1.git.0.09f6c01.el7.noarch

Comment 7 errata-xmlrpc 2018-12-13 19:27:05 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2018:3748