Cluster status is Not Ready after GitRepo showing Active status

[sbulage]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

GitRepo showing status Active after deploying applications to respective clusters. But Clusters are not updating their status immediately instead showing Not Ready state.

Expected Behavior

Cluster status should be updated in sync with GitRepo status.

Steps To Reproduce

1. Create a GitRepo (may be) targeting to local cluster.
2. Wait for the application to be deployed to the local cluster.
3. Go to Continuous Delivery --> Clusters
4. See the status of the local cluster it is in Not Ready state. (See attached screenshot for more detailed information)

Environment

- Architecture:
- Fleet Version: 0.10.0-rc.1
- Cluster:
  - Provider:k3s
  - Options:
  - Kubernetes Version:

Logs

Anything else?

It is not happening in Rancher 2.8 or 2.7.

Screenshot:

• kubectl output:
  

• Actual Screenshot
  

[slickwarren]

some other testing shows that forcing an update on the clusterGroups will update the resource count.

[sbulage]

System Information

Rancher Version	Fleet Version
v2.9-head	104.0.2+up0.10.2-rc.1

---

Steps followed from the description

1. Create a GitRepo (may be) targeting to local cluster.
2. Wait for the application to be deployed to the local cluster.
3. Go to Continuous Delivery --> Clusters
4. Verified that the status of the local cluster is Active in-sync with GitRepo status.

---

Screenshot/Video

See below video for more detail (Check downstream cluster status using cluster groups)

cluster_status_using_cluster_group.mp4