Bug 2059491

Summary:	[IPI on Alibabacloud] The format of the metadata.name is wrong
Product:	OpenShift Container Platform	Reporter:	husun <husun>
Component:	Installer	Assignee:	OCP Installer <ocp-installer>
Installer sub component:	openshift-installer	QA Contact:	Jianli Wei <jiwei>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	low
Priority:	medium	CC:	beth.white, padillon
Version:	4.10
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 01:13:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description husun 2022-03-01 07:41:21 UTC

Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version:

$ openshift-install version
<your output here>

Platform: Alibabacloud

#Please specify the platform type: aws, libvirt, openstack or baremetal etc.

Please specify: IPI

What happened?
Not all zone IDs are connected using "-", such as the availability zone ID ap-southeast-6a, and the ap-southeast-6 is region ID.

So removing the prefix via "<region id>-" may fail



What did you expect to happen?
The format of name is fixed, such as: <cluster ID>-<role>-<zoone ID>

#Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

#Enter text here.

Comment 1 Jianli Wei 2022-04-06 11:24:02 UTC

Tested with the build having the PR https://github.com/openshift/installer/pull/5668 (see https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-gcp-modern/1511585318749343744), and everything is ok.


https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/91618/ (SUCCESS, region ap-southeast-5)

$ oc get clusterversion
NAME      VERSION                                                   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.ci.test-2022-04-06-094513-ci-ln-qz4qkkt-latest   True        False         10m     Cluster version is 4.11.0-0.ci.test-2022-04-06-094513-ci-ln-qz4qkkt-latest
$ oc get machinesets -A
NAMESPACE               NAME                                     DESIRED   CURRENT   READY   AVAILABLE   AGE
openshift-machine-api   jiwei-303-rdh78-worker-ap-southeast-5a   1         1         1       1           37m
openshift-machine-api   jiwei-303-rdh78-worker-ap-southeast-5b   1         1         1       1           37m
openshift-machine-api   jiwei-303-rdh78-worker-ap-southeast-5c   0         0                             37m
$ oc get machines -A
NAMESPACE               NAME                                           PHASE     TYPE            REGION           ZONE              AGE
openshift-machine-api   jiwei-303-rdh78-master-0                       Running   ecs.g6.xlarge   ap-southeast-5   ap-southeast-5a   37m
openshift-machine-api   jiwei-303-rdh78-master-1                       Running   ecs.g6.xlarge   ap-southeast-5   ap-southeast-5b   37m
openshift-machine-api   jiwei-303-rdh78-master-2                       Running   ecs.g6.xlarge   ap-southeast-5   ap-southeast-5c   37m
openshift-machine-api   jiwei-303-rdh78-worker-ap-southeast-5a-sfm92   Running   ecs.g6.large    ap-southeast-5   ap-southeast-5a   28m
openshift-machine-api   jiwei-303-rdh78-worker-ap-southeast-5b-hszcn   Running   ecs.g6.large    ap-southeast-5   ap-southeast-5b   28m
$ 


https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/91620/ (SUCCESS, region cn-hangzhou)

$ oc get clusterversion
NAME      VERSION                                                   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.ci.test-2022-04-06-094513-ci-ln-qz4qkkt-latest   True        False         9m25s   Cluster version is 4.11.0-0.ci.test-2022-04-06-094513-ci-ln-qz4qkkt-latest
$ oc get machinesets -A
NAMESPACE               NAME                                   DESIRED   CURRENT   READY   AVAILABLE   AGE
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-h   0         0                             38m
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-i   1         1         1       1           38m
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-j   0         0                             38m
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-k   1         1         1       1           38m
$ oc get machines -A
NAMESPACE               NAME                                         PHASE     TYPE            REGION        ZONE            AGE
openshift-machine-api   jiwei-304-x4lbj-master-0                     Running   ecs.g6.xlarge   cn-hangzhou   cn-hangzhou-k   38m
openshift-machine-api   jiwei-304-x4lbj-master-1                     Running   ecs.g6.xlarge   cn-hangzhou   cn-hangzhou-i   38m
openshift-machine-api   jiwei-304-x4lbj-master-2                     Running   ecs.g6.xlarge   cn-hangzhou   cn-hangzhou-j   38m
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-i-hb8qp   Running   ecs.g6.large    cn-hangzhou   cn-hangzhou-i   27m
openshift-machine-api   jiwei-304-x4lbj-worker-cn-hangzhou-k-x8s4r   Running   ecs.g6.large    cn-hangzhou   cn-hangzhou-k   27m
$

Comment 4 Shiftzilla 2023-03-09 01:13:42 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9136