Bug 2080172 - Still create policy automation successfully when the PolicyAutomation name exceed 63 characters
Summary: Still create policy automation successfully when the PolicyAutomation name ex...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.5
Assignee: Robert Howington
QA Contact: Xiang Yin
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-29 07:28 UTC by yahliu
Modified: 2022-06-09 02:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:11:57 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 22090 0 None None None 2022-04-29 09:48:53 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:12:08 UTC

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
Note You need to log in before you can comment on or make changes to this bug.