Version: 4.10 Platform: ibmcloud Please specify: IPI What happened? The IBM Cloud provider expects the ResourceGroupName is injected into the cloud-provider-config configmap. Without it, the CCM fails. What did you expect to happen? IBM CCM runs properly, initiating masters and workers for workloads. How to reproduce it (as minimally and precisely as possible)? IPI deployment on IBM Cloud using existing 4.10 releases # openshift-install create cluster Anything else we need to know? IBM Cloud is working on a fix to inject the ResourceGroupName into the cloudproviderconfig
[Pre-merge QA Summary] [Version] ~~~ $ ./openshift-install-local version ./openshift-install-local unreleased-master-5105-gb018924f1f97737518147bf6088e3463f9c7ceb9 built from commit b018924f1f97737518147bf6088e3463f9c7ceb9 release image registry.ci.openshift.org/origin/release:4.8 release architecture amd64 ~~~ [Parameters] ~~~ apiVersion: v1 baseDomain: ibmcloud.qe.devcluster.openshift.com compute: - architecture: amd64 hyperthreading: Enabled name: worker platform: ibmcloud: {} replicas: 0 controlPlane: architecture: amd64 hyperthreading: Enabled name: master platform: ibmcloud: type: bx2-8x32 replicas: 3 metadata: creationTimestamp: null name: pamoedo-test networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineNetwork: - cidr: 10.0.0.0/16 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16 platform: ibmcloud: region: eu-de resourceGroupName: pamoedom-rg publish: External pullSecret: sshKey: ~~~ [Results] ~~~ $ ./openshift-install-local create manifests --dir test39/ --log-level debug DEBUG OpenShift Installer unreleased-master-5105-gb018924f1f97737518147bf6088e3463f9c7ceb9 DEBUG Built from commit b018924f1f97737518147bf6088e3463f9c7ceb9 ... DEBUG Generating Openshift Manifests... INFO Manifests created in: test39/manifests and test39/openshift $ grep "ResourceGroup" test39/manifests/cloud-provider-config.yaml g2ResourceGroupName = pamoedom-rg ~~~ *** PASSED ***
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