-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17.0
-
Moderate
-
No
-
False
-
-
MAPI for IBM Cloud currently only checks the first group of subnets (50) when searching for subnet details by name. If unable to find the subnet and retrieve it's ID, MAPI will be unable to create/manage cluster nodes.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-43675. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-36698. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-36185. The following is the description of the original issue:
—
Description of problem:
The MAPI 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. Create a new IPI cluster (with or without BYON)
3. MAPI will attempt to find Subnet details by name, likely failing as it only checks the first group (50)...depending on order returned by IBM Cloud API
Actual results:
MAPI fails to find Subnet ID, thus cannot create/manage cluster nodes.
Expected results:
Successful IPI deployment.
Additional info:
IBM Cloud is working on a patch to MAPI to handle the ListSubnets API call and pagination results.
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
