Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1838885

Summary:	GCP: the resources are created with identifier prefix that removes almost all context of cluster name
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Installer	Assignee:	Abhinav Dahiya <adahiya>
Installer sub component:	openshift-installer	QA Contact:	Yang Yang <yanyang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high
Version:	4.5
Target Milestone:	---
Target Release:	4.4.z
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:	2020-06-17 22:26:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1837642
Bug Blocks:	1838886

Description OpenShift BugZilla Robot 2020-05-22 01:39:58 UTC

+++ This bug was initially created as a clone of Bug #1837642 +++

Description of problem:

On GCP all resources are prefixed with infra-id, which currently is 12 chars with 6 chars used by random bit, leaving only 6 chars from cluster name. This causes trouble associating the cluster to jobs in CI as most of the identifyable characters are dropped from the resource names in CI due to this restriction.

Also because of the previous restriction, only one char are used from pool's name, making is highly likely to collide in cases there are more.

Comment 4 Yang Yang 2020-05-29 14:19:03 UTC

Verified with 4.4.0-0.nightly-2020-05-29-065458

1. Set cluster name to yangyang1838885 and install a cluster 
2. Check the nodes name
# oc get node
NAME                                                           STATUS   ROLES    AGE   VERSION
yangyang1838885-9wl65-master-0.c.openshift-qe.internal         Ready    master   47m   v1.17.1
yangyang1838885-9wl65-master-1.c.openshift-qe.internal         Ready    master   47m   v1.17.1
yangyang1838885-9wl65-master-2.c.openshift-qe.internal         Ready    master   47m   v1.17.1
yangyang1838885-9wl65-worker-a-vrxpn.c.openshift-qe.internal   Ready    worker   40m   v1.17.1
yangyang1838885-9wl65-worker-b-597kd.c.openshift-qe.internal   Ready    worker   40m   v1.17.1
yangyang1838885-9wl65-worker-c-xkp4s.c.openshift-qe.internal   Ready    worker   40m   v1.17.1

3. Set cluster name to yangyang1838885yangyang and install a cluster 
4. Check the nodes name
# oc get node
NAME                                                           STATUS   ROLES    AGE   VERSION
yangyang1838885yangya-vt92r-master-0.c.openshift-qe.internal   Ready    master   38m   v1.17.1
yangyang1838885yangya-vt92r-master-1.c.openshift-qe.internal   Ready    master   38m   v1.17.1
yangyang1838885yangya-vt92r-master-2.c.openshift-qe.internal   Ready    master   38m   v1.17.1
yangyang1838885yangya-vt92r-worker-a-4297n                     Ready    worker   26m   v1.17.1
yangyang1838885yangya-vt92r-worker-b-qtkgn                     Ready    worker   26m   v1.17.1
yangyang1838885yangya-vt92r-worker-c-5j6mk                     Ready    worker   26m   v1.17.1

The infra-id uses at most 21 characters from the cluster name and hence move it to verified state.

Comment 8 errata-xmlrpc 2020-06-17 22:26:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, 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/RHBA-2020:2445