Bug 1446737
Summary: | [3.5] Redeploy certificates fails with custom openshift_hosted_router_certificate | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Andrew Butcher <abutcher> | |
Component: | Installer | Assignee: | Andrew Butcher <abutcher> | |
Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.5.1 | CC: | aos-bugs, gpei, jialiu, jokerman, mmccomas | |
Target Milestone: | --- | |||
Target Release: | 3.5.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously, replacement of router certificates through use of the certificate redeployment playbook (playbooks/byo/openshift-cluster/redeploy-certificates.yml) or the router certificate redeployment playbook (playbooks/byo/openshift-cluster/redeploy-router-certificates.yml) would fail when a custom router certificate was provided. Custom router certificates set by openshift_hosted_router_certificate within the inventory may now be redeployed.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1446741 1446745 (view as bug list) | Environment: | ||
Last Closed: | 2017-12-14 21:01:55 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: | 1446741, 1446745 |
Description
Andrew Butcher
2017-04-28 17:15:25 UTC
Proposed fix: https://github.com/openshift/openshift-ansible/pull/4037 Verify this bug with openshift-ansible-3.5.65-1.git.0.da18a47.el7.noarch With custom router certificate provided during install via openshift_hosted_router_certificate, then redeploy cert against the cluster, custom router cert would be retained and router pod was running well. 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:3438 |