Bug 2080172

Summary:	Still create policy automation successfully when the PolicyAutomation name exceed 63 characters
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	yahliu
Component:	Console	Assignee:	Robert Howington <rhowingt>
Status:	CLOSED ERRATA	QA Contact:	Xiang Yin <xiyin>
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	unspecified
Version:	rhacm-2.5	CC:	dho, dhuynh, huichen
Target Milestone:	---	Flags:	bot-tracker-sync: rhacm-2.5+
Target Release:	rhacm-2.5
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:	2022-06-09 02:11:57 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:

Comment 1 bot-tracker-sync 2022-05-03 20:35:24 UTC

G2Bsync 1116303855 comment 
 RobDolares Tue, 03 May 2022 16:36:18 UTC 
 `G2Bsync` @gparvin - Please verify and close

the secret creation was updated to be comparable to 2.4.
We are already putting a 63 character limit on `policyName.namespace`.  So if policy is created with a maximum 63-char limit - the longest policy automation name would be `73`, which is still allowed by kubernetes.

fyi @yahliu @jamestalton

Comment 2 bot-tracker-sync 2022-05-09 22:00:06 UTC

G2Bsync 1121510122 comment 
 gparvin Mon, 09 May 2022 19:49:36 UTC 
 G2Bsync The secret looks correct to me on build `2.5.0-SNAPSHOT-2022-05-09-05-56-04`.  Thanks for making the fix.  Since QE opened this issue I'll let QE close it.

Comment 3 yahliu 2022-05-10 08:46:52 UTC

Verified on 2.5.0-DOWNSTREAM-2022-05-08-12-27-27

Comment 7 errata-xmlrpc 2022-06-09 02:11:57 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 (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), 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/RHSA-2022:4956