Bug 1999734

Summary:	IBM Cloud CIS Instance CRN missing in infrastructure manifest/resource
Product:	OpenShift Container Platform	Reporter:	Christopher J Schaefer <cschaefe>
Component:	Installer	Assignee:	aos-install
Installer sub component:	openshift-installer	QA Contact:	Pedro Amoedo <pamoedom>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	mstaeble, pamoedom, rvanderp
Version:	4.10
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:06:30 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 Christopher J Schaefer 2021-08-31 16:40:27 UTC

Version: 4.9.0

$ openshift-install version
4.9

Platform:

ibmcloud

Please specify:
IPI

What happened?

During an IBM Cloud IPI deployment, the `ingress-operator` was expecting the Infrastructure/cluster to contain the IBM Cloud CIS Instance CRN.
It appears the `installer` does not have the support to add that data to the `infrastructure` manifest and requires an update from `openshift/api` to pull in the infrastructure type changes as well.


What did you expect to happen?

The `installer` should be populated the `infrastructure` manifest with the IBM Cloud CIS Instance CRN.

How to reproduce it (as minimally and precisely as possible)?

$ openshift-install create cluster
wait for the cluster deployment to reach operator bring up and check `ingress-operator` logs that it expects CIS CRN from `infrastructure/cluster` resource.

Anything else we need to know?

IBM is developing a fix to inject this data into the `infrastructure` manifest.

Comment 10 errata-xmlrpc 2022-03-10 16:06:30 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