Version: $ openshift-install version openshift-install 4.10.0-0.nightly-2022-01-29-015515 built from commit 4fc9fa88c22221b6cede2456b1c33847943b75c9 release image registry.ci.openshift.org/ocp/release@sha256:b6bded497818f2e07401988576f15c62cd6fe45c385d177b50a43d6dabaf4524 release architecture amd64 Platform: alibabacloud Please specify: * IPI What happened? "aliyun slb DescribeRegions" doesn't tell the 2 regions, so no way to deploy OCP cluster. What did you expect to happen? Suggest to confirm with Ali DEV, and see if the 2 regions should be removed for now from the supported regions list. How to reproduce it (as minimally and precisely as possible)? Always. Anything else we need to know? We got the error after https://bugzilla.redhat.com/show_bug.cgi?id=2041750 is fixed. > the errors told by installer (https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/72114/): 01-29 17:02:52.822 level=error msg=Error: [ERROR] terraform-provider-alicloud/alicloud/resource_alicloud_slb_load_balancer.go:324: Resource alicloud_slb_load_balancer CreateLoadBalancer Failed!!! [SDK alibaba-cloud-sdk-go ERROR]: 01-29 17:02:52.822 level=error msg=SDKError: 01-29 17:02:52.822 level=error msg= StatusCode: 400 01-29 17:02:52.822 level=error msg= Code: InvalidParameter 01-29 17:02:52.822 level=error msg= Message: code: 400, The specified RegionId does not exist. request id: 01AF203E-8CCD-5A9A-BFD0-3F3CE6FF4551 01-29 17:02:52.822 level=error msg= Data: {"Code":"InvalidParameter","HostId":"slb.cn-guangzhou.aliyuncs.com","Message":"The specified RegionId does not exist.","Recommend":"https://error-center.aliyun.com/status/search?Keyword=InvalidParameter\u0026source=PopGw","RequestId":"01AF203E-8CCD-5A9A-BFD0-3F3CE6FF4551"} 01-29 17:02:52.822 level=error 01-29 17:02:52.822 level=error 01-29 17:02:52.822 level=error msg= on ../../../../../../../../tmp/openshift-install-cluster-2044588525/vpc/slb.tf line 2, in resource "alicloud_slb_load_balancer" "slb_external": 01-29 17:02:52.823 level=error msg= 2: resource "alicloud_slb_load_balancer" "slb_external" { 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error msg=Error: [ERROR] terraform-provider-alicloud/alicloud/resource_alicloud_slb_load_balancer.go:324: Resource alicloud_slb_load_balancer CreateLoadBalancer Failed!!! [SDK alibaba-cloud-sdk-go ERROR]: 01-29 17:02:52.823 level=error msg=SDKError: 01-29 17:02:52.823 level=error msg= StatusCode: 400 01-29 17:02:52.823 level=error msg= Code: InvalidParameter 01-29 17:02:52.823 level=error msg= Message: code: 400, The specified RegionId does not exist. request id: 8F6160FF-6560-5F46-8069-EDF0CE052799 01-29 17:02:52.823 level=error msg= Data: {"Code":"InvalidParameter","HostId":"slb.cn-guangzhou.aliyuncs.com","Message":"The specified RegionId does not exist.","Recommend":"https://error-center.aliyun.com/status/search?Keyword=InvalidParameter\u0026source=PopGw","RequestId":"8F6160FF-6560-5F46-8069-EDF0CE052799"} 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error msg= on ../../../../../../../../tmp/openshift-install-cluster-2044588525/vpc/slb.tf line 44, in resource "alicloud_slb_load_balancer" "slb_internal": 01-29 17:02:52.823 level=error msg= 44: resource "alicloud_slb_load_balancer" "slb_internal" { 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=error 01-29 17:02:52.823 level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change >FYI the vailable regions of slb $ aliyun slb DescribeRegions --output cols=RegionId,RegionEndpoint rows=Regions.Region[] RegionId | RegionEndpoint -------- | -------------- cn-hangzhou | slb.aliyuncs.com cn-shanghai | slb.aliyuncs.com cn-qingdao | slb.aliyuncs.com cn-beijing | slb.aliyuncs.com cn-zhangjiakou | slb.cn-zhangjiakou.aliyuncs.com cn-huhehaote | slb.cn-huhehaote.aliyuncs.com cn-shenzhen | slb.aliyuncs.com cn-heyuan | slb.cn-heyuan.aliyuncs.com cn-chengdu | slb.cn-chengdu.aliyuncs.com cn-hongkong | slb.aliyuncs.com ap-southeast-1 | slb.aliyuncs.com ap-southeast-2 | slb.ap-southeast-2.aliyuncs.com ap-southeast-3 | slb.ap-southeast-3.aliyuncs.com ap-southeast-5 | slb.ap-southeast-5.aliyuncs.com ap-northeast-1 | slb.ap-northeast-1.aliyuncs.com ap-south-1 | slb.ap-south-1.aliyuncs.com eu-central-1 | slb.eu-central-1.aliyuncs.com eu-west-1 | slb.eu-west-1.aliyuncs.com us-west-1 | slb.aliyuncs.com us-east-1 | slb.aliyuncs.com me-east-1 | slb.me-east-1.aliyuncs.com ap-southeast-6 | slb.ap-southeast-6.aliyuncs.com $ >FYI the vailable regions of ecs and vpc respectively $ aliyun ecs DescribeRegions --output cols=RegionId,RegionEndpoint rows=Regions.Region[] RegionId | RegionEndpoint -------- | -------------- cn-qingdao | ecs.cn-qingdao.aliyuncs.com cn-beijing | ecs.cn-beijing.aliyuncs.com cn-zhangjiakou | ecs.cn-zhangjiakou.aliyuncs.com cn-huhehaote | ecs.cn-huhehaote.aliyuncs.com cn-wulanchabu | ecs.cn-wulanchabu.aliyuncs.com cn-hangzhou | ecs.aliyuncs.com cn-shanghai | ecs.cn-shanghai.aliyuncs.com cn-shenzhen | ecs.cn-shenzhen.aliyuncs.com cn-heyuan | ecs.cn-heyuan.aliyuncs.com cn-guangzhou | ecs.cn-guangzhou.aliyuncs.com cn-chengdu | ecs.cn-chengdu.aliyuncs.com cn-hongkong | ecs.cn-hongkong.aliyuncs.com ap-northeast-1 | ecs.ap-northeast-1.aliyuncs.com ap-southeast-1 | ecs.ap-southeast-1.aliyuncs.com ap-southeast-2 | ecs.ap-southeast-2.aliyuncs.com ap-southeast-3 | ecs.ap-southeast-3.aliyuncs.com ap-southeast-6 | ecs.ap-southeast-6.aliyuncs.com ap-southeast-5 | ecs.ap-southeast-5.aliyuncs.com ap-south-1 | ecs.ap-south-1.aliyuncs.com us-east-1 | ecs.aliyuncs.com us-west-1 | ecs.aliyuncs.com eu-west-1 | ecs.eu-west-1.aliyuncs.com me-east-1 | ecs.me-east-1.aliyuncs.com eu-central-1 | ecs.eu-central-1.aliyuncs.com cn-nanjing | ecs.cn-nanjing.aliyuncs.com $ aliyun vpc DescribeRegions --output cols=RegionId,RegionEndpoint rows=Regions.Region[] RegionId | RegionEndpoint -------- | -------------- cn-qingdao | vpc.aliyuncs.com cn-beijing | vpc.aliyuncs.com cn-zhangjiakou | vpc.cn-zhangjiakou.aliyuncs.com cn-huhehaote | vpc.cn-huhehaote.aliyuncs.com cn-wulanchabu | vpc.cn-wulanchabu.aliyuncs.com cn-hangzhou | vpc.aliyuncs.com cn-shanghai | vpc.aliyuncs.com cn-shenzhen | vpc.aliyuncs.com cn-guangzhou | vpc.cn-guangzhou.aliyuncs.com cn-hongkong | vpc.aliyuncs.com ap-northeast-1 | vpc.ap-northeast-1.aliyuncs.com ap-southeast-1 | vpc.aliyuncs.com ap-southeast-2 | vpc.ap-southeast-2.aliyuncs.com ap-southeast-3 | vpc.ap-southeast-3.aliyuncs.com ap-southeast-5 | vpc.ap-southeast-5.aliyuncs.com ap-south-1 | vpc.ap-south-1.aliyuncs.com us-east-1 | vpc.aliyuncs.com us-west-1 | vpc.aliyuncs.com me-east-1 | vpc.me-east-1.aliyuncs.com eu-central-1 | vpc.eu-central-1.aliyuncs.com ap-southeast-6 | vpc.ap-southeast-6.aliyuncs.com cn-chengdu | vpc.cn-chengdu.aliyuncs.com eu-west-1 | vpc.eu-west-1.aliyuncs.com cn-heyuan | vpc.cn-heyuan.aliyuncs.com $
FYI using China-portal account, the 2 regions do support SLB $ aliyun --config-path ${ALI_CN_CONFIG} slb DescribeRegions --output cols=RegionId,RegionEndpoint rows=Regions.Region[] RegionId | RegionEndpoint -------- | -------------- cn-hangzhou | slb.aliyuncs.com cn-shanghai | slb.aliyuncs.com cn-qingdao | slb.aliyuncs.com cn-beijing | slb.aliyuncs.com cn-zhangjiakou | slb.cn-zhangjiakou.aliyuncs.com cn-huhehaote | slb.cn-huhehaote.aliyuncs.com >cn-wulanchabu | slb.cn-wulanchabu.aliyuncs.com cn-shenzhen | slb.aliyuncs.com cn-heyuan | slb.cn-heyuan.aliyuncs.com >cn-guangzhou | slb.cn-guangzhou.aliyuncs.com cn-chengdu | slb.cn-chengdu.aliyuncs.com cn-hongkong | slb.aliyuncs.com ap-southeast-1 | slb.aliyuncs.com ap-southeast-2 | slb.ap-southeast-2.aliyuncs.com ap-southeast-3 | slb.ap-southeast-3.aliyuncs.com ap-southeast-5 | slb.ap-southeast-5.aliyuncs.com ap-northeast-1 | slb.ap-northeast-1.aliyuncs.com ap-south-1 | slb.ap-south-1.aliyuncs.com eu-central-1 | slb.eu-central-1.aliyuncs.com eu-west-1 | slb.eu-west-1.aliyuncs.com us-west-1 | slb.aliyuncs.com us-east-1 | slb.aliyuncs.com me-east-1 | slb.me-east-1.aliyuncs.com ap-southeast-6 | slb.ap-southeast-6.aliyuncs.com $
There is no SLB service in Region Guangzhou and Wulanchabu for International site account. For 410, we do not need to support these two regions for the user who is using an International site account. Domestic site account support for these two regions is enough. We can list this restriction into the document.
Cloned to Jira project https://issues.redhat.com/browse/OCPBUGS-2385