This message was deleted.

Did you solve this?

I think the cluster was stuck... hard to remember that far back on the issue

kubectl get <http://clusters.management.cattle.io|clusters.management.cattle.io>  # find the cluster you want to delete 
export CLUSTERID="c-xxxxxxxxx" # 
kubectl patch <http://clusters.management.cattle.io|clusters.management.cattle.io> $CLUSTERID -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl delete <http://clusters.management.cattle.io|clusters.management.cattle.io> $CLUSTERID

That un-sticks a cluster. Now, if the cluster itself just never retries, you can bounce the rancher server pods, and that starts a new "registration phase" on all clusters when they boot back up. (At your own risk of course) - Sometimes you can just make an edit to your downstream cluster yaml and that will kick it off too.