This is a clone of issue OCPBUGS-45303. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45301. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45289. The following is the description of the original issue:
—
Description of problem:
The LB name should be yunjiang-ap55-sk6jl-ext-a6aae262b13b0580, rather than ending with ELB service endpoint (elb.ap-southeast-5.amazonaws.com): failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed provisioning resources after infrastructure ready: failed to find HostedZone ID for NLB: failed to list load balancers: ValidationError: The load balancer name 'yunjiang-ap55-sk6jl-ext-a6aae262b13b0580.elb.ap-southeast-5.amazonaws.com' cannot be longer than '32' characters\n\tstatus code: 400, request id: f8adce67-d844-4088-9289-4950ce4d0c83 Checking the tag value, the value of Name key is correct: yunjiang-ap55-sk6jl-ext
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-30-141716
How reproducible:
always
Steps to Reproduce:
1. Deploy a cluster on ap-southeast-5 2. 3.
Actual results:
The LB can not be created
Expected results:
Create a cluster successfully.
Additional info:
No such issues on other AWS regions.
- clones
-
OCPBUGS-45303 Incorrect ELB name was recognized by installer on ap-southeast-5
- ASSIGNED
- is blocked by
-
OCPBUGS-45303 Incorrect ELB name was recognized by installer on ap-southeast-5
- ASSIGNED