Bug 1607391 - Router is not redeployed after redeploy-certificates playbook
Summary: Router is not redeployed after redeploy-certificates playbook
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.0
Assignee: Vadim Rutkovsky
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks: 1601376
TreeView+ depends on / blocked
 
Reported: 2018-07-23 12:37 UTC by Vadim Rutkovsky
Modified: 2018-10-11 07:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:22:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:22:29 UTC

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
Note You need to log in before you can comment on or make changes to this bug.