Bug 2101453 - 64 character length causing clusters to unsubscribe
Summary: 64 character length causing clusters to unsubscribe
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: rhacm-2.5.1
Assignee: Xiangjing Li
QA Contact: Almen Ng
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-27 14:20 UTC by Jamie Parker
Modified: 2022-07-07 14:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-07 14:48:12 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 23766 0 None None None 2022-06-27 14:40:30 UTC
Red Hat Product Errata RHSA-2022:5531 0 None None None 2022-07-07 14:48:18 UTC

Description Jamie Parker 2022-06-27 14:20:30 UTC
Description of the problem: A 64 character resource name limit is causing ACM to see resource names as duplicates when the names exceed the 64 character limit.

Release version: 2.5

Operator snapshot version:

OCP version:

Browser Info:

Steps to reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 1 juhsu 2022-06-27 14:40:31 UTC
Will also be delivered as a hotfix in advance of 2.5.1 at customer's request because it is impacting their ability to manage their environment.

Comment 2 juhsu 2022-06-28 13:30:53 UTC
Based on a meeting with the Jamie, Haim, and CEE, on June 27 this fix will only be delivered in 2.5.1 because the customer requesting the hotfix does not have support entitlement.  Sales, Devin, sent an email to the customer to get this addressed.  They will let Eng know asap if the status changes, and a hotfix is still required.

Comment 8 errata-xmlrpc 2022-07-07 14:48:12 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 (Moderate: Red Hat Advanced Cluster Management 2.5.1 security updates 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:5531


Note You need to log in before you can comment on or make changes to this bug.