Bug 2107049 - The clusterrole for global clusterset did not created by default
Summary: The clusterrole for global clusterset did not created by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.6
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: rhacm-2.6
Assignee: Le Yang
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-14 08:29 UTC by Hui Chen
Modified: 2022-09-06 22:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-06 22:33:43 UTC
Target Upstream Version:
Embargoed:
huichen: qe_test_coverage+
bot-tracker-sync: rhacm-2.6+
cbynum: rhacm-2.6.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24286 0 None None None 2022-07-14 12:03:18 UTC
Red Hat Product Errata RHSA-2022:6370 0 None None None 2022-09-06 22:33:53 UTC

Comment 1 Hui Chen 2022-07-15 06:45:43 UTC 
The issue seems caused by we did not have webhook to update the global clusterset, but relay on the reconciled to check the update back. so there have a time interval that the global clusterset will be use LegacyClusterSetLabel in a short time window.
Comment 2 Hui Chen 2022-08-16 10:15:39 UTC 
Verified using 2.1.0-DOWNANDBACK-2022-08-11-23-42-45
Comment 5 errata-xmlrpc 2022-09-06 22:33:43 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.6.0 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:6370
Note You need to log in before you can comment on or make changes to this bug.