Bug 1544952

Summary: [DOCS] Steps to manually redeploy router certs missing steps
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED DUPLICATE QA Contact: Vikram Goyal <vigoyal>
Severity: high Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: unspecifiedCC: aos-bugs, jokerman, mmccomas, stwalter
Target Milestone: ---   
Target Release: ---   
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-06-18 05:58:43 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:

Description Eric Jones 2018-02-13 20:28:02 UTC 
Document URL: 
[0] https://docs.openshift.com/container-platform/3.6/install_config/redeploying_certificates.html#redeploying-router-certificates-manually

[1] https://docs.openshift.com/container-platform/3.6/install_config/router/default_haproxy_router.html#manually-redeploy-certs

Section Number and Name:
Installation and Configuration 
Redeploying Certificates
Redeploying Registry or Router Certificates Only
REDEPLOYING ROUTER CERTIFICATES MANUALLY

Describe the issue: 
In the redeploying cert guide, we have a section about manually redeploying the certs for the registry and the router [0]. The registry section is fine as it does include all of the settings, but the router directions do not.

Suggestions for improvement:
So either update that section to include all of the steps, like in this portion of the docs [1] or in this kcs [2], or just point directly to this portion of the docs [1] where it is already provided.

Additional information: 

[2] https://access.redhat.com/solutions/2650171
Comment 1 Steven Walter 2018-04-16 20:14:15 UTC 
This might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1465049 -- please verify
Comment 2 Vikram Goyal 2018-06-18 05:58:43 UTC 

*** This bug has been marked as a duplicate of bug 1465049 ***