Bug 2039085

Summary:	Cloud credential operator configuration failing to apply in hypershift/ROKS clusters
Product:	OpenShift Container Platform	Reporter:	Cesar Wong <cewong>
Component:	ibm-roks-toolkit	Assignee:	Cesar Wong <cewong>
Status:	CLOSED ERRATA	QA Contact:	Jie Zhao <jiezhao>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10
Target Milestone:	---
Target Release:	4.10.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:38:34 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:	2046582

Description Cesar Wong 2022-01-10 22:12:29 UTC

Description of problem:
In hypershift clusters, the CloudCredential.configuration.openshift.io CRD is not provisioned. However, the CVO attempts to apply a manifest with an instance of that CRD to the target cluster because the instance is not excluded.

Version-Release number of selected component (if applicable):
4.10

How reproducible:
Always

Steps to Reproduce:
1. Extract the latest 4.10 nightly release payload
2. Inspect 0000_50_cloud-credential-operator_01-operator-config.yaml in the payload

Actual results:
The 0000_50_cloud-credential-operator_01-operator-config.yaml file contains the following annotation:
  include.release.openshift.io/ibm-cloud-managed: "true"

Expected results:
The 0000_50_cloud-credential-operator_01-operator-config.yaml does not contain the annotation.

Additional info:

Comment 6 errata-xmlrpc 2022-03-10 16:38:34 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056