Description of problem:
The installer for IBM Cloud currently only checks the first group of subnets (50) when searching for Subnet details by name. It should provide pagination support to search all subnets.
Version-Release number of selected component (if applicable):
4.17
How reproducible:
100%, dependent on order of subnets returned by IBM Cloud API's however
Steps to Reproduce:
1. Create 50+ IBM Cloud VPC Subnets
2. Use Bring Your Own Network (BYON) configuration (with Subnet names for CP and/or Compute) in install-config.yaml
3. Attempt to create manifests (openshift-install create manifests)
Actual results:
ERROR failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [platform.ibmcloud.controlPlaneSubnets: Not found: "eu-de-subnet-paginate-1-cp-eu-de-1", platform.ibmcloud.controlPlaneSubnets: Not found: "eu-de-subnet-paginate-1-cp-eu-de-2", platform.ibmcloud.controlPlaneSubnets: Not found: "eu-de-subnet-paginate-1-cp-eu-de-3", platform.ibmcloud.controlPlaneSubnets: Invalid value: []string{"eu-de-subnet-paginate-1-cp-eu-de-1", "eu-de-subnet-paginate-1-cp-eu-de-2", "eu-de-subnet-paginate-1-cp-eu-de-3"}: number of zones (0) covered by controlPlaneSubnets does not match number of provided or default zones (3) for control plane in eu-de, platform.ibmcloud.computeSubnets: Not found: "eu-de-subnet-paginate-1-compute-eu-de-1", platform.ibmcloud.computeSubnets: Not found: "eu-de-subnet-paginate-1-compute-eu-de-2", platform.ibmcloud.computeSubnets: Not found: "eu-de-subnet-paginate-1-compute-eu-de-3", platform.ibmcloud.computeSubnets: Invalid value: []string{"eu-de-subnet-paginate-1-compute-eu-de-1", "eu-de-subnet-paginate-1-compute-eu-de-2", "eu-de-subnet-paginate-1-compute-eu-de-3"}: number of zones (0) covered by computeSubnets does not match number of provided or default zones (3) for compute[0] in eu-de]
Expected results:
Successful manifests and cluster creation
Additional info:
IBM Cloud is working on a fix
- blocks
-
OCPBUGS-43329 [IBMCloud] install only checks first set of subnets (no pagination support)
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
-
RHEA-2024:6122
OpenShift Container Platform 4.18.z bug fix update
[OCPBUGS-36236] [IBMCloud] install only checks first set of subnets (no pagination support)
version: 4.18.0-0.nightly-2024-10-27-185104
created 51 subnets ref https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/pr-logs/pull/openshift_release/58092/rehearse-58092-periodic-ci-openshift-verification-tests-master-installation-nightly-4.18-ibmcloud-ipi-mult-subnets-f28/1850782774542209024/artifacts/ibmcloud-ipi-mult-subnets-f28/ibmcloud-provision-vpc-mult-subnets/build-log.txt
the last subnet：
ci-op-15nv9h2g-02490-control-plane-jp-tok-3
create a cluster using 6 subnets, succeed.
install config:
platform:
ibmcloud:
region: jp-tok
networkResourceGroupName: ci-op-15nv9h2g-02490-rg
vpcName: ci-op-15nv9h2g-02490-vpc
controlPlaneSubnets:
- ci-op-15nv9h2g-02490-control-plane-jp-tok-3
- ci-op-15nv9h2g-02490-control-plane-jp-tok-2
- ci-op-15nv9h2g-02490-control-plane-jp-tok-1
computeSubnets:
- ci-op-15nv9h2g-02490-compute-jp-tok-3
- ci-op-15nv9h2g-02490-compute-jp-tok-2
- ci-op-15nv9h2g-02490-compute-jp-tok-1
resourceGroupName: ci-op-15nv9h2g-02490-rg
version:
4.18.0-0.nightly-2024-10-23-112324
based on the default vpc, add 45 subnet in one zone.
the manifest created succeeds.
but when creating the cluster got the error:
level=error msg=Cluster operator ingress Degraded is True with IngressDegraded: The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: 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-18a-7d762-711c4e6ae98b485594c9ebb3bf3a7cf7 for service openshift-ingress/router-default with UID 711c4e6a-e98b-4855-94c9-ebb3bf3a7cf7: Failed ensuring LoadBalancer: Invalid json payload provided: Message: Validation Failure for field: subnets Code: validation_failed_max_items TargetName: subnets TargetType: field TargetValue:...
validation_failed_max_items error, whether has the limitation in the LB? and the installer configure should based on the limitation to do pre-check
cschaefe@redhat.com jeffbnowicki whether this bug need to be added to the release doc? if need, could you help add more? thanks
OpenShift Jira Bot
added a comment - Hi jeffbnowicki,
Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.
OpenShift Jira Bot
added a comment - Hi jeffbnowicki ,
Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified. 
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.18.1 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.
https://access.redhat.com/errata/RHSA-2024:6122