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:
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.
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
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
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/
Thanks for sharing. It's interesting and informative. https://www.livetheorangelife.net/