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

Bug 1426888

Summary:	[3.3] Stop restarting node after upgrading master rpms
Product:	OpenShift Container Platform	Reporter:	Takayoshi Tanaka <tatanaka>
Component:	Cluster Version Operator	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.1	CC:	aos-bugs, jokerman, mmccomas, ssiddiqu, trogers
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously the node service was restarted immediately after updating the master. This restart is not deferred until after the node upgrade steps have been completed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-05 08:53:15 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:
Bug Blocks:	1267746

Description Takayoshi Tanaka 2017-02-26 05:16:43 UTC

Description of problem:
OpenShift 3.3 user is facing an issue of deployment. The upstream issue [1] may cause this issue.
https://github.com/openshift/openshift-ansible/pull/2593

OpenShift 3.4 has been merged this issue, 

Version-Release number of selected component (if applicable):
oc v3.3.1.14
playbook version 3.3.61-1.git.0.27743e6.el7

How reproducible:
Has not confirmed on my environment

Steps to Reproduce:
1. Install a new OpenShift cluster with multi masters and nodes 

Actual results:
playbook run without error, but some nodes are NotReady status.
They are complaining that they are unable to "get routes" for tun0. This device is absent at this point.

I'll paste the customer's log in my next private comment.

Expected results:
All nodes are Ready status.


Additional info:
Is it an available workaround to edit a local playbook directory to patch the PR? 
https://github.com/openshift/openshift-ansible/pull/2593/files

Comment 3 Scott Dodson 2017-02-27 15:57:26 UTC

https://github.com/openshift/openshift-ansible/pull/3501

Comment 5 Scott Dodson 2017-03-02 21:03:51 UTC

We'd already merged the backport, may as well test and release it.

Comment 7 Anping Li 2017-03-08 09:34:59 UTC

All nodes are in ready status after upgrade by atomic-openshift-utils-3.3.68. So move bug to verified.

Comment 9 errata-xmlrpc 2017-04-05 08:53:15 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-2017:0883