Bug 2061527 - [IBMCloud] infrastructure asset missing CloudProviderType
Summary: [IBMCloud] infrastructure asset missing CloudProviderType
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Nobody
QA Contact: MayXu
Depends On:
Blocks: 2062429
TreeView+ depends on / blocked
Reported: 2022-03-07 18:58 UTC by Christopher J Schaefer
Modified: 2022-08-10 10:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Cause: The infra asset was missing the ProviderType field on IBMCloud installations that was used by the cluster Consequence: etcd operator was not picking the right configuration for IBMCloud clusters Fix: Added a field in the infra asset set to IBMCloud. Result: etcd operator seems to pick the right configuration now.
Clone Of:
Last Closed: 2022-08-10 10:52:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5687 0 None open Bug 2061527: IBMCloud: Missing infra providertype 2022-03-08 01:39:27 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:53:04 UTC

Description Christopher J Schaefer 2022-03-07 18:58:05 UTC

$ openshift-install version


Please specify:

What happened?
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

platform: IBMCloud
      cisInstanceCRN: foo
      location: us-east
      resourceGroupName: foo
    type: IBMCloud

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

Comment 2 MayXu 2022-03-10 16:37:55 UTC
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"'
  "Ibmcloud": {
    "Cis Instance CRN": "crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::",
    "Location": "eu-gb",
    "Provider Type": "VPC",
    "Resource Group Name": "maxu-1527-6w225"
  "Type": "IBMCloud"

Platform Status:
      Cis Instance CRN:     crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::
      Location:             eu-gb
      Provider Type:        VPC
      Resource Group Name:  maxu-1527-6w225
    Type:                   IBMCloud

Comment 5 errata-xmlrpc 2022-08-10 10:52:44 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 (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.


Note You need to log in before you can comment on or make changes to this bug.