Bug 1824921
Summary: | Incorrect Instructions for refreshing CA cert bundle | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | egarcia |
Component: | Installer | Assignee: | egarcia |
Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | dsanzmor, m.andre, mbridges, pprinett, wjiang, wsun |
Version: | 4.3.z | ||
Target Milestone: | --- | ||
Target Release: | 4.3.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The oc command for refreshing the CA cert is missing the resource type on which to operate.
Consequence: The command returns an error.
Fix: Correct the command by adding the missing configmap resource type.
Result: The command now succeeds.
|
Story Points: | --- |
Clone Of: | 1824917 | Environment: | |
Last Closed: | 2020-04-30 01:28:30 UTC | Type: | --- |
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: | 1824917 | ||
Bug Blocks: |
Description
egarcia
2020-04-16 16:44:12 UTC
Verified Temporarily reverting the status to allow for the automation to allow the merge Move the bug to ON_QA for verification. Checked and it's fixed. https://github.com/openshift/installer/tree/release-4.3/docs/user/openstack#refreshing-a-ca-certificate Refreshing a CA Certificate If you ran the installer with a custom CA certificate, then this certificate can be changed while the cluster is running. To change your certificate, edit the value of the ca-cert.pem key in the cloud-provider-config configmap with a valid PEM certificate. oc edit configmap -n openshift-config cloud-provider-config 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-2020:1529 |