Bug 1607391

Summary:	Router is not redeployed after redeploy-certificates playbook
Product:	OpenShift Container Platform	Reporter:	Vadim Rutkovsky <vrutkovs>
Component:	Installer	Assignee:	Vadim Rutkovsky <vrutkovs>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, gpei, jokerman, mmccomas, wmeng
Target Milestone:	---
Target Release:	3.11.0
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-10-11 07:22:06 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:	1601376

Description Vadim Rutkovsky 2018-07-23 12:37:37 UTC

Description of problem:

Router redeployment is not triggered after redeploy-certificates playbook is run. Manual redeploy would cause routers to break, as it 

Version-Release number of the following components:
openshift-ansible 3.11
ansible 2.6


How reproducible:
Always

Steps to Reproduce:
1. Deploy OCP/Origin
2. Run redeploy-certificates
3. Check router dc status

Actual results:
No new deployment triggered

Expected results:
New deployment triggered, router works correctly

Comment 1 Vadim Rutkovsky 2018-07-23 13:34:57 UTC

PR for master - https://github.com/openshift/openshift-ansible/pull/9301

Comment 2 Vadim Rutkovsky 2018-08-10 07:57:25 UTC

Fix is available in openshift-ansible-3.11.0-0.13.0

Comment 3 Gaoyun Pei 2018-08-13 09:52:45 UTC

Verify this bug with openshift-ansible-3.11.0-0.13.0.git.0.16dc599None.noarch

After router redeploy-certificates playbook, router pod is redeployed, router-certs secret was updated. No error logs in router pod and app's route is available.

Comment 5 errata-xmlrpc 2018-10-11 07:22:06 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:2652