Stuck for more than 30mins on TASK [Resource Readiness Check]

[RKolibri]

Hi,
I was trying to deploy a cluster with 1 master and 3 workers everything goes fine except when i run the task ansible:install
it goes through and get stuck at TASK [Resource Readiness Check]. Still waiting if anything comes up .
If i ssh into the master i can get the nodes and pods that are currently running and the VIP is also up i can ping it normally .

This is the second time deploying those are the results of below commands

kubectl get nodes 

- NAME          STATUS   ROLES                       AGE   VERSION
- k3s-master0   Ready    control-plane,etcd,master   22m   v1.27.1+k3s1
- k3s-node1     Ready    <none>                      21m   v1.27.1+k3s1
- k3s-node2     Ready    <none>                      21m   v1.27.1+k3s1
- k3s-node3     Ready    <none>                      21m   v1.27.1+k3s1


 kubectl get pods -A
- NAMESPACE         NAME                                       READY   STATUS    RESTARTS      AGE
- calico-system     calico-kube-controllers-56cfd7598d-qvfdt   1/1     Running   0             20m
- calico-system     calico-node-2vhlg                          1/1     Running   0             19m
- calico-system     calico-node-4lhdz                          1/1     Running   0             19m
- calico-system     calico-node-4nl6t                          1/1     Running   0             19m
- calico-system     calico-node-5ctvg                          1/1     Running   0             20m
- calico-system     calico-typha-78d9b4f656-v25dc              1/1     Running   0             20m
- calico-system     calico-typha-78d9b4f656-z4fgm              1/1     Running   0             19m
- calico-system     csi-node-driver-7zh8b                      2/2     Running   0             20m
- calico-system     csi-node-driver-l77hq                      2/2     Running   0             19m
- calico-system     csi-node-driver-lwgdt                      2/2     Running   0             19m
- calico-system     csi-node-driver-xd9ht                      2/2     Running   0             19m
- kube-system       coredns-77ccd57875-jsfg9                   1/1     Running   0             20m
- kube-system       kube-vip-4s2nn                             1/1     Running   1 (20m ago)   20m
- tigera-operator   tigera-operator-549d4f9bdb-54w2z           1/1     Running   1 (20m ago)   20m 

Thanks in advance

[onedr0p]

I've recently made some changes around this, overall the resource readiness check should take around 30s-1m. I slimmed down some of the prom operator crds so it should be quicker.

You look to be fine, I would just make sure you clean up the custom-* manifests in the var/lib/rancher/k3s/server/manifests on the master nodes.

[RKolibri]

That's what i did i checked the steps on the playbook and did them manually working fine so far
but still curious why is it happening.
Thanks a lot