cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1120
Views
0
Helpful
6
Replies

DNAC Installation Stuck at “Wait for Kubernetes Control plane to start

zmtechnologie
Level 1
Level 1

 

Hello everyone,

I'm encountering an issue during the installation of Cisco DNA Center on my server. Although all the necessary system requirements (CPU, RAM, storage, etc.) are met, the installation process gets stuck at the following step:

FAILED - RETRYING: Wait for Kubernetes Control plane to start functioning (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 300, "changed": true, "cmd": "kubectl get nodes --kubeconfig \"/home/maglev/.kube/config\""}

 

6 Replies 6

gernotstoiser
Level 1
Level 1

I have tha same issue. Tried OVA with 2.3.7.6 and 2.3.7.5 in our lab env. Always ends up the same error. Did you fix this issue?

2.3.7.7 worked ok for me. 2.3.7.5 ended up with the same error you had.

julian.bendix
Spotlight
Spotlight

Which version? 2.3.7.9?

Virtual or Appliance?

balaji.bandi
Hall of Fame
Hall of Fame

As long as the all the resources are correct it take some time and also you have internet connectivity working.

I did some installation all went as expected virtual and Physical appliance.

Note : check some important notes in the blog.

https://www.balajibandi.com/?p=2515

BB

=====Preenayamo Vasudevam=====

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

gernotstoiser
Level 1
Level 1

In my case the behavior is because of insufficient CPU.

Our lab environment is older, and the CPU can't provide 64000MHz reservation, The VM couldn't even start with that value, so I cut it in half to 32000MHz. Which was enough to start the VM and the CatC install process, but not enough for Kubernetes during install.
Now I set the reservation to 41000. Since then, CatC is working so far. Hope this helps some with the same problems.

Thx for all the input and help!

If resources are properly allocated and Software version is higher than 2.3.7.7 then check NTP server is properly configured and clock is in sync.