Bug 1838886

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 DEFERRED	Docs Contact:
Severity:	high
Priority:	high	CC:	wking
Version:	4.5
Target Milestone:	---
Target Release:	4.3.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-07-15 00:31:21 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:	1838885
Bug Blocks:

Description OpenShift BugZilla Robot 2020-05-22 01:40:09 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 1 Scott Dodson 2020-05-29 00:24:08 UTC

4.4.z PR is in the merge queue, even if it merges tonight, goes to VERIFIED I think we're fine waiting on this until next week. I'd rather not rush a fix to 4.4.z and 4.3.z in the same week.

Comment 4 Scott Dodson 2020-07-15 00:31:21 UTC

This was fixed in 4.4.8 but won't be backported to 4.3.