Hi Ricardo, Can you try logging into your control node using: ssh -i /var/cloudstack/management/.ssh/id_rsa -p 2222 cloud@<public IP>
If you've used an ssh key, pass the key that's associated with the cluster instead of the Management server's private key. Once logged in, can you check status of the deploy-kube-system service using: systemctl status deploy-kube-system You may also be able to debug the issue further by checking the daemon.log file in the control node Regards, Pearl ________________________________ From: Wei ZHOU <[email protected]> Sent: July 26, 2024 12:45 PM To: [email protected] <[email protected]> Subject: Re: Kubernetes in creating state Is the public IP of CKS cluster reachable from the mgmt server ? as far as I know, in some users' environment, the public IPs and private IPs are mutually unreachable. -Wei On Fri, Jul 26, 2024 at 6:03 PM Ricardo Pertuz <[email protected]> wrote: > > Thanks Kiran, > > I did that and even consulting the database parameter > > | name | value | > +--------------+---------------------------------------+ > +--------------+---------------------------------------+ > | endpoint.url | http://192.168.x.x:8080/client/api | > +--------------+---------------------------------------+ > > but still getting the "The connection to the server localhost:8080 was > refused - did you specify the right host or port?" I made sure I have the > connection right also the right NetworkOffering and the ACL en Allow ALL just > for testing but not working, anything else I can check? > > Ricardo Pertuz > CTO > > > > > > 25 de julio de 2024, 20:30, "Kiran Chavala" <[email protected]> > escribió: > > > > > > > Hi Ricardo > > > > Please set the global settings value of “Endpoint url (endpoint.url)” to > > the management server ip address > > > > http://<management/ server ip > > >:8080/client/api<http://10.1.35.31:8080/client/api> > > http://10.1.35.31:8080/client/api%3E > > > > Regards > > > > Kiran > > > > From: Ricardo Pertuz <[email protected]> > > > > Date: Friday, 26 July 2024 at 4:16 AM > > > > To: [email protected] <[email protected]> > > > > Subject: Kubernetes in creating state > > > > Hi, > > > > On my ACS KVM 4.19.0.1 I'm creating a Kubernetes cluster v 1.24, the nodes > > are created successfully but the cluster remains in "Starting" phase, in > > the logs I see only the following warning > > > > 2024-07-25 17:08:30,682 WARN [c.c.k.c.u.KubernetesClusterUtil] > > (API-Job-Executor-1:ctx-cd6974d9 job-7508 ctx-a6104520) (logid:4314dc5d) > > Failed to retrieve ready node count for Kubernetes cluster : kubernetes01 > > > > 024-07-25 17:08:30,033 DEBUG [c.c.k.c.u.KubernetesClusterUtil] > > (API-Job-Executor-1:ctx-cd6974d9 job-7508 ctx-a6104520) (logid:4314dc5d) > > Checking ready nodes for the Kubernetes cluster : kubernetes01 with total 2 > > provisioned nodes > > > > java.lang.NumberFormatException: For input string: "0 > > > > The connection to the server localhost:8080 was refused - did you specify > > the right host or port?" > > > > at > > java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > > > > https://java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > > > > at java.base/java.lang.Integer.parseInt(Integer.java:652) > > https://java.base/java.lang.Integer.parseInt(Integer.java:652) > > > > at java.base/java.lang.Integer.parseInt(Integer.java:770) > > https://java.base/java.lang.Integer.parseInt(Integer.java:770) > > > > at > > com.cloud.kubernetes.cluster.utils.KubernetesClusterUtil.getKubernetesClusterReadyNodesCount(KubernetesClusterUtil.java:220) > > > > at > > com.cloud.kubernetes.cluster.utils.KubernetesClusterUtil.validateKubernetesClusterReadyNodesCount(KubernetesClusterUtil.java:290) > > > > at > > com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterStartWorker.startKubernetesClusterOnCreate(KubernetesClusterStartWorker.java:552) > > > > at > > com.cloud.kubernetes.cluster.KubernetesClusterManagerImpl.startKubernetesCluster(KubernetesClusterManagerImpl.java:1321) > > > > at > > org.apache.cloudstack.api.command.user.kubernetes.cluster.CreateKubernetesClusterCmd.execute(CreateKubernetesClusterCmd.java:294) > > > > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:172) > > > > at > > com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:112) > > > > at > > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:654) > > > > at > > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) > > > > at > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) > > > > at > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) > > > > at > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) > > > > at > > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) > > > > at > > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:602) > > > > at > > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > > > > https://java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > > > > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > > https://java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > > > > at > > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > > > > https://java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > > > > at > > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > > > > https://java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > > > > at java.base/java.lang.Thread.run(Thread.java:829) > > https://java.base/java.lang.Thread.run(Thread.java:829) > > > > Ricardo Pertuz > >
