-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.19
-
Informational
-
None
-
False
-
-
-
Known Issue
-
Proposed
Description of problem:
install cluster in ca-mon region with the default vm type failed, need specify the vm type
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Always
Steps to Reproduce:
1. ipi install cluster on ca-mon region, vm type use the default
platform:
ibmcloud:
region: ca-mon
Actual results:
install failed, have not found any vm in the resource group: level=debug msg="found bootstrap address: []" level=debug msg="master machine manifests found: [/home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/.clusterapi_output/Machine-openshift-cluster-api-guests-maxu-ca-mon-19-qzn6x-master-0.yaml /home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/.clusterapi_output/Machine-openshift-cluster-api-guests-maxu-ca-mon-19-qzn6x-master-1.yaml /home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/install-dir/.clusterapi_output/Machine-openshift-cluster-api-guests-maxu-ca-mon-19-qzn6x-master-2.yaml]" level=debug msg="found master address: []" level=debug msg="found master address: []" level=debug msg="found master address: []" level=error msg="Attempted to gather debug logs after installation failure: must provide bootstrap host address" level=error msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to provision control-plane machines: machines are not ready: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline" ~
Expected results:
install succeed
Additional info:
specify the vm type to the bx3d-4x20 or other vm types which support in ca-mon install $oc get co | grep -v "True .*False .*False" NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.19.0-0.nightly-2025-05-19-005500 False False True 74m OAuthServerRouteEndpointAccessibleControllerAvailable: Get "https://oauth-openshift.apps.maxu-mon-19-p.private-ibmcloud.qe.devcluster.openshift.com/healthz": Service Unavailable console 4.19.0-0.nightly-2025-05-19-005500 False True True 58m DeploymentAvailable: 0 replicas available for console deployment RouteHealthAvailable: failed to GET route (https://console-openshift-console.apps.maxu-mon-19-p.private-ibmcloud.qe.devcluster.openshift.com): Get "https://console-openshift-console.apps.maxu-mon-19-p.private-ibmcloud.qe.devcluster.openshift.com": Service Unavailable ingress False True True 71m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: LoadBalancerReady=False (SyncLoadBalancerFailed: The service-controller component is reporting SyncLoadBalancerFailed events like: Error syncing load balancer: failed to ensure load balancer: Error on cloud load balancer kube-maxu-mon-19-p-czxxv-61f46158dac944d08b6d80d05a54bd1d for service openshift-ingress/router-default with UID 61f46158-dac9-44d0-8b6d-80d05a54bd1d: Failed getting LoadBalancer: Get "https://ca-mon.private.iaas.cloud.ibm.com/v1/load_balancers?generation=2&version=2024-12-17": Service Unavailable The cloud-controller-manager logs may contain more details.) 2. checked with pre-merge build on 4.18 has the same issue.
