$ openshift-install version
During IPI install on IBM Cloud, the "infrastructure/cluster" asset is incomplete, resulting in components that rely on the infrastructure to not work properly
After a successful IPI install, the PlatformStatus does not contain a proper CloudProviderType, as would be expected
Which should contain a "providerType"
Where valid values are
What did you expect to happen?
A properly configured "infrastructure/cluster" asset, including a CloudProviderType, to be used by other components/operators for determining configuration, etc. based on IBM Cloud.
How to reproduce it (as minimally and precisely as possible)?
1. Create a new IPI cluster on IBM Cloud
2. Check the "infrastructure/cluster" asset (oc describe infrastructure/cluster)
Anything else we need to know?
IBM Cloud is already testing a fix and will be providing a PR with said fix.
This is likely affecting the configuration for cluster-etcd-operator, based on this missing value
checked on 4.11.0-0.nightly-2022-03-10-094942
$oc describe infrastructure/cluster > i.yaml
add "" in the i.yaml Lin 69 to resolve the following error.
$ oc describe infrastructure/cluster | yq
yq: Error running jq: ScannerError: mapping values are not allowed in this context
in "<stdin>", line 69, column 144.
$ cat i.yaml | yq '.Status."Platform Status"'
"Cis Instance CRN": "crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::",
"Provider Type": "VPC",
"Resource Group Name": "maxu-1527-6w225"
Cis Instance CRN: crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::
Provider Type: VPC
Resource Group Name: maxu-1527-6w225
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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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.