Cluster in not-ready state after fixing a wrong Gitrepo URL

[mmartin24]

Issue

While checking other issue, it was noticed that when fixing a wrong URL from a Gitrepo, the cluster remains in NotReady state

Steps to reproduce:

• Deploy Rancher 2.9
• Deploy a Girepo that will produce an error, for instance with a space:

Repository URL: `https://github.com/rancher/fleet-test-data ` (notice the space at the end)
Branch: `master`
Paths: `qa-test-apps/nginx-app`

• Wait until fails
• Fix it by removing the space
• Wait until is corrected
• Go to Continuous Delivery > Clusters

Observed behavior

Cluster in Not Ready status for a long, long time

Screencast.from.05-07-24.17.23.39.webm

---

Test environment:

Single cluster Rancher: v2.9-1d34dbcbf674228c8e63d10449c6da35d8d16692-head
Fleet version: fleet:104.0.0+up0.10.0-rc.19
K8s: v1.28.8 +k3s1

[0xavi0]

I think this is an issue in the rancher UI, not Fleet

I can also reproduce it:

But when checking with kubectl the status of the cluster is correct:

$ kubectl get clusters -A                                                                                                                        
NAMESPACE     NAME    READY   KUBECONFIG
fleet-local   local   true    local-kubeconfig

Bundles....

$ kubectl get bundles -n fleet-local                                                                                                             
NAME                BUNDLEDEPLOYMENTS-READY   STATUS
fleet-agent-local   1/1
test-simple         1/1

GitRepos...

kubectl get gitrepos -A                                                                                                                        
NAMESPACE     NAME   REPO                                        COMMIT                                     BUNDLEDEPLOYMENTS-READY   STATUS
fleet-local   test   https://github.com/rancher/fleet-examples   2ada7cca738877df8459b3a34839a15e5683edaa   1/1

[kkaempf]

@nwmac ptal