Bug 1824917

Summary: Incorrect Instructions for refreshing CA cert bundle
Product: OpenShift Container Platform Reporter: egarcia
Component: InstallerAssignee: egarcia
Installer sub component: OpenShift on OpenStack QA Contact: David Sanz <dsanzmor>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: eduen, m.andre, pprinett
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.0   
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:
: 1824921 1824927 (view as bug list) Environment:
Last Closed: 2020-05-04 11:49:21 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: 1824927    
Bug Blocks: 1824921    

Description egarcia 2020-04-16 16:32:33 UTC
The instructions for refreshing the CA cert have a typo. The instructions state to run: oc edit -n openshift-config cloud-provider-config however this command is incorrect. It should be: oc edit configmap -n openshift-config cloud-provider-config

Comment 3 David Sanz 2020-04-17 09:34:50 UTC
Verified

Comment 4 Pierre Prinetti 2020-04-18 10:37:45 UTC
Temporarily reverting the status to allow for the automation to link the PR

Comment 6 Pierre Prinetti 2020-04-20 17:33:23 UTC
The PR is merged; status can be moved back to VERIFIED.

Comment 7 David Sanz 2020-04-21 09:03:45 UTC
Verified

Comment 9 errata-xmlrpc 2020-05-04 11:49:21 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-2020:0581