Hi Pahrial,

In this kind of scenario, I would use the Cluster API command to get the kubeconfig of the cluster

```

clusterctl -n magnum-system get kubeconfig kube-r6jnx

```

Store the output of that and try doing a `kubectl get nodes` or `kubectl get pods -A` and see if the API server is up and if there is any issues within the cluster (if certain pods are not up or not ready).

Thanks

Mohammed

From: pahrialtkj@gmail.com <pahrialtkj@gmail.com>
Date: Thursday, May 2, 2024 at 11:06 AM
To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: [magnum-cluster-api] CREATE_IN_PROGRESS never ending

Hi all,

I created a k8s cluster using magnum-cluster-api in openstack bobcat , I used kind for the capi (kind on top of lxc), magnum has been successfully installed along with the cluster-api, but when I create a k8s cluster it is always in the CREATE_IN_PROGRESS status and never completes, if you look at the loadbalancer and the master/worker server has been successfully provisioned, if in the show cluster it looks:
status_reason        | CAPI Cluster status: Provisioned: Cluster kube-r6jnx is Provisioned. CAPI OpenstackCluster status reason:

And when I check the capi-system capi-controller-manager, it always say : http: TLS handshake error from 10.244.0.1:9005: EOF
full log https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsprunge.us%2FDgnUOE&data=05%7C02%7Cmnaser%40vexxhost.com%7C46a1a6e26f224d0d3dc008dc6ab95803%7C54e2b12264054dafa35bf65edc45c621%7C0%7C0%7C638502592075725406%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C80000%7C%7C%7C&sdata=m2DAnY9BHmx%2BalP2nltvbROeVpjEaLbgXty1jEGSYSc%3D&reserved=0



Regards,
Pahrial