Bug 2079533

Summary:	Clusters with no default clusterset do not get assigned default cluster when upgrading from ACM 2.4 to 2.5
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	dhuynh
Component:	Cluster Lifecycle	Assignee:	Jian Qiu <jqiu>
Status:	CLOSED ERRATA	QA Contact:	Hui Chen <huichen>
Severity:	high	Docs Contact:	Christopher Dawson <cdawson>
Priority:	high
Version:	rhacm-2.5	CC:	alisauxbpn53, dhuynh, trieudinhqt1057, yuhe
Target Milestone:	---	Flags:	dhuynh: 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:44 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:

Description dhuynh 2022-04-27 17:41:25 UTC

Description of the problem:
When a cluster is imported/created and does not have a clusterset in 2.4.z, we expect it to be placed in the default clusterset when ACM is upgraded to 2.5. We can observe that clusters that are not local-cluster do not get placed in default clusterset after upgrade.

Release version:
ACM 2.4.3-DOWNSTREAM-2022-04-13-07-05-00  → 2.5.0-DOWNSTREAM-2022-04-26-10-05-22

OCP version:
Hub AWS (FIPS enabled) OCP 4.10.9

Steps to reproduce:
1. Import an EKS cluster into ACM 2.4.3 with no clusterset assigned
2. Upgrade ACM to 2.5
3. observe EKS does not have default clusterset

Actual results:
clusters with no clusterset before upgrade still don't have clusterset after acm upgraded to 2.5

Expected results:
clusters with no clusterset get assigned default clusterset

Additional info:

Comment 1 dhuynh 2022-04-27 18:15:32 UTC

The cluster without clusterset after upgrade can still be added to clustersets post-upgrade, and if removed from a clusterset will then be placed in default set.

Comment 2 dhuynh 2022-05-04 03:01:55 UTC

No longer seeing this issue after upgrade from 2.4.3-DOWNSTREAM-2022-04-13-07-05-00  → 2.5.0-DOWNSTREAM-2022-05-02-16-00-32

Comment 5 errata-xmlrpc 2022-06-09 02:11:44 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

Comment 6 Edith Stewart 2023-01-12 06:47:55 UTC Comment hidden (spam)

Red Hat Advanced Cluster Management for Kubernetes provides the capabilities to address common challenges that administrators and site reliability engineers face as they work across a range of public and private cloud environments. Clusters and applications are all visible and managed from a single console—with security policy built in.

https://www.tellculvers.org/

Comment 7 Leona R. Boyd 2023-07-31 10:39:51 UTC Comment hidden (spam)

Thanks for sharing. It's interesting and informative. https://www.livetheorangelife.net/