GitHub user n4l5u0r created a discussion: VR only starts to work at 100% after migration
Hello, I have an issue on a VR which is created as part of default: DefaultNetworkOfferingforKubernetesService. when I create it and launch CKS in it I have an issue of never achieving `Running` state of the CKS cluster which stays in `Starting`state. If I launch CKS without specifying a network it creates it by itself and same issue. But once I migrate the created VR from one KVM to another then everything is smooth and works perfectly, I achieve the `Running`state instantly no matter the configuration of the post deployment of the CKS on this network. So I don't understand what is wrong with the initial VR startup which looks like not having the full config until a migration happens. It looks like it is a network misconfiguration as if deploy the VR without any migration and establish a ssh tunnel between the KVM hosting the VR and the mgmt 8080 endpoint then it works without going though a migration. I am on `4.20.0.2` and using `1.33.1-calico-Kubernetes-Binaries-ISO` So it looks like the VR does not have the full network topology at start and receive it at migration... is it possible to have a workaround without using and ssh tunnel neither using migration. GitHub link: https://github.com/apache/cloudstack/discussions/12209 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
