G2Bsync 1115136426 comment 
 KevinFCormier Mon, 02 May 2022 17:12:52 UTC 
 G2Bsync

The root cause of this is that the `local-cluster-cluster-secret` in the `openshift-gitops` namespace has a blank name and address in the labels:

```
kind: Secret
apiVersion: v1
metadata:
  name: local-cluster-cluster-secret
  namespace: openshift-gitops
  uid: c7d3c4b8-3417-427f-bbbe-fb7c0128280c
  resourceVersion: '2025438'
  creationTimestamp: '2022-04-29T19:53:59Z'
  labels:
    apps.open-cluster-management.io/acm-cluster: 'true'
    apps.open-cluster-management.io/cluster-name: ''
    apps.open-cluster-management.io/cluster-server: ''
    argocd.argoproj.io/secret-type: cluster
  managedFields:
    - manager: gitopscluster
      operation: Update
      apiVersion: v1
      time: '2022-04-29T19:53:59Z'
      fieldsType: FieldsV1
      fieldsV1:
        f:data:
          .: {}
          f:config: {}
          f:name: {}
          f:server: {}
        f:metadata:
          f:labels:
            .: {}
            f:apps.open-cluster-management.io/acm-cluster: {}
            f:apps.open-cluster-management.io/cluster-name: {}
            f:apps.open-cluster-management.io/cluster-server: {}
            f:argocd.argoproj.io/secret-type: {}
        f:type: {}
```

@rokej @xiangjingli Can someone from app lifecycle check why this is happening?

This is also revealing a bug in `search-api` where these blank values can hide the correct matching cluster secret for other clusters.

https://github.com/stolostron/search-api/blob/release-2.4/src/v2/models/application.js#L138

Fixing this can resolve the issue for other clusters, but not for local-cluster itself:
![image](https://user-images.githubusercontent.com/42188127/166293237-756dbe22-bd97-4a9b-8b8a-8dbd85b9b680.png)

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.4.5 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:5201