Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1795037

Summary:	[OpenStack] CAPO fails to get cloud-provider CA cert
Product:	OpenShift Container Platform	Reporter:	Martin André <m.andre>
Component:	Installer	Assignee:	Martin André <m.andre>
Installer sub component:	OpenShift on OpenStack	QA Contact:	David Sanz <dsanzmor>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	unspecified
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:26:45 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 Martin André 2020-01-26 15:38:08 UTC

CAPO should be able to read the `openshift-config/cloud-provider-config` configmap in order to retrieve the cloud provider CA certificate.

This should have been handled in https://github.com/openshift/machine-api-operator/pull/473/, however there was a typo (clustermap vs clustermaps) and the new cloud-provider-config-reader role doesn't allow reading from the config map.

Here is the error from the CAPO logs:

I0125 17:54:30.807499       1 machineservice.go:189] Not using cloud provider CA cert: failed to get configmap openshift-config/cloud-provider-config/ca-bundle.pem from kubernetes api: configmaps "cloud-provider-config" is forbidden: User "system:serviceaccount:openshift-machine-api:machine-api-controllers" cannot get resource "configmaps" in API group "" in the namespace "openshift-config"

Comment 1 Martin André 2020-02-04 13:16:48 UTC

The original PR at https://github.com/openshift/machine-api-operator/pull/480 was superseded by https://github.com/openshift/machine-api-operator/pull/471 which merged already.
Moving to ON_QA.

Comment 2 David Sanz 2020-02-04 13:52:44 UTC

Verified on 4.4.0-0.nightly-2020-01-31-144949

Comment 4 errata-xmlrpc 2020-05-04 11:26:45 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