Bug 2070846

Summary: [ACM 2.5] Can't re-add the default clusterset label after removing it from a managedcluster on BM SNO hub
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Song Lai <slai>
Component: Cluster LifecycleAssignee: Jian Qiu <jqiu>
Status: CLOSED ERRATA QA Contact: Hui Chen <huichen>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: high    
Version: rhacm-2.5CC: dhuynh, yuhe
Target Milestone: ---Flags: bot-tracker-sync: 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:10:23 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 Song Lai 2022-04-01 07:52:13 UTC 
Description of the problem:
Can't set the default clusterset label to a managedcluster after removing the default clusterset. 



```
% oc get managedcluster --show-labels
NAME                           HUB ACCEPTED   MANAGED CLUSTER URLS                                         JOINED   AVAILABLE   AGE     LABELS
acmqe-test-automation-ls2l2b   false          https://acmqe-test-automation.com                                                 70s     cluster.open-cluster-management.io/clusterset=,feature.open-cluster-management.io/addon-observability-controller=unreachable,feature.open-cluster-management.io/addon-work-manager=unreachable,name=acmqe-test-automation-ls2l2b
```


Release version:
2.5

Operator snapshot version:
2.5.0-DOWNSTREAM-2022-03-29-05-04-50

OCP version:
4.10.3

Browser Info:
Firefox

Steps to reproduce:
1. import a cluster
2. check the default set label have added
3. remove the set label, the name of set label is null

Actual results:
default set label cannot be added

Expected results:
default set label can be added again.

Additional info:
Comment 1 bot-tracker-sync 2022-04-02 08:22:12 UTC 
G2Bsync 1086573447 comment 
 elgnay Sat, 02 Apr 2022 07:19:02 UTC 
 G2Bsync
I can not reproduce the issue on the BM SNO hub. @laisongls Are my steps different from yours?
```sh
[centos@ylctos8x 21335]$ kubectl get managedcluster cluster-21335 --show-labels
NAME            HUB ACCEPTED   MANAGED CLUSTER URLS   JOINED   AVAILABLE   AGE     LABELS
cluster-21335   false                                                      4m31s   cluster.open-cluster-management.io/clusterset=default,name=cluster-21335
[centos@ylctos8x 21335]$ kubectl label managedcluster cluster-21335 cluster.open-cluster-management.io/clusterset= --overwrite
managedcluster.cluster.open-cluster-management.io/cluster-21335 labeled
[centos@ylctos8x 21335]$ kubectl get managedcluster cluster-21335 --show-labels
NAME            HUB ACCEPTED   MANAGED CLUSTER URLS   JOINED   AVAILABLE   AGE     LABELS
cluster-21335   false                                                      4m48s   cluster.open-cluster-management.io/clusterset=,name=cluster-21335
[centos@ylctos8x 21335]$ kubectl label managedcluster cluster-21335 cluster.open-cluster-management.io/clusterset=default --overwrite
managedcluster.cluster.open-cluster-management.io/cluster-21335 labeled
[centos@ylctos8x 21335]$ kubectl get managedcluster cluster-21335 --show-labels
NAME            HUB ACCEPTED   MANAGED CLUSTER URLS   JOINED   AVAILABLE   AGE    LABELS
cluster-21335   false                                                      5m5s   cluster.open-cluster-management.io/clusterset=default,name=cluster-21335
```
Comment 2 bot-tracker-sync 2022-04-06 11:09:40 UTC 
G2Bsync 1090066595 comment 
 elgnay Wed, 06 Apr 2022 09:39:45 UTC 
 G2Bsync the fix has been merged. Please verify with the latest build.
Comment 3 Song Lai 2022-04-13 06:36:02 UTC 
verified with build 2.5.0-DOWNSTREAM-2022-04-12-15-23-11
Comment 6 errata-xmlrpc 2022-06-09 02:10:23 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 7 Eboni Booker 2023-02-07 09:09:47 UTC Comment hidden (spam)