Kubernetes cluster recipes not seeing nodes
-
xoa.recipe.createKubernetesCluster { "masterName": "K8S Master", "nbNodes": 3, "network": "37559e16-f83d-b1f4-a1ae-b9c3336dca22", "sr": "a20ee08c-40d0-9818-084f-282bbca1f217", "sshKey": "ssh-ed25519 AAAAC3NzaC1lZDI1Nhbilj;jojj'hufsdklk,kp;joFWlpk8BlpKpTO3T2R44YHP6b+g Kubernetes cluster" } { "code": "SR_BACKEND_FAILURE_46", "params": [ "", "The VDI is not available [opterr=Failed to attach VDI during \"prepare thin\": The VDI is not available [opterr=Plugin linstor-manager failed]]", "" ], "call": { "method": "VM.start", "params": [ "OpaqueRef:6ae3475f-7455-4328-904d-168b35b8ce5f", false, false ] }, "message": "SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=Failed to attach VDI during \"prepare thin\": The VDI is not available [opterr=Plugin linstor-manager failed]], )", "name": "XapiError", "stack": "XapiError: SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=Failed to attach VDI during \"prepare thin\": The VDI is not available [opterr=Plugin linstor-manager failed]], ) at Function.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/_XapiError.js:16:12) at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/transports/json-rpc.js:35:21" }
-
Okay so your problem isn't k8s recipe related, but elsewhere (probably the storage).
-
@olivierlambert said in Kubernetes cluster recipes not seeing nodes:
Okay so your problem isn't k8s recipe related, but elsewhere (probably the storage).
Yup.. I just ran the K8S recipe on local storage and I have cluster..
debian@master:~$ kubectl get node NAME STATUS ROLES AGE VERSION master Ready control-plane 20m v1.26.3 node-1 Ready <none> 5m24s v1.26.3 node-2 Ready <none> 7m32s v1.26.3 node-3 Ready <none> 4m18s v1.26.3
Issue seem to be with the XOSTOR SR. Any chance @ronan-a could test if the K8S recipe work on his XOSTOR SR? I just want to know if it is specific to my setup or XOSTOR in general (bug)
-
-
I think it's totally unrelated. If you have issues to create the XO Hub Debian 11 VM, nothing else could work after that.
-
@olivierlambert said in Kubernetes cluster recipes not seeing nodes:
If you have issues to create the XO Hub Debian 11 VM, nothing else could work after that.
What do you mean? I can create XO Hub Debian 11 on XOSTOR with no issue. I am not sure I understand you ?
-
What I mean is the fact that the issue with your k8s recipe is not related to the recipe itself, but a problem on your own XOSTOR cluster.
-
@olivierlambert said in Kubernetes cluster recipes not seeing nodes:
What I mean is the fact that the issue with your k8s recipe is not related to the recipe itself, but a problem on your own XOSTOR cluster.
How can we be sure its not a bug and only and issue with my system? This is way i was asking if anyone else running XOSTOR could try to confirm the issue is with my system
-
Because we identified some issues on XOSTOR recently, and that's exactly what causing your issue. If the VM doesn't boot, there's 0 chance the k8s recipe can work.
-
@olivierlambert ok so is it a matter to create K8S on local storage and moved them manually to XOSTOR untill XOSTOR issue get a fix?
-
I would advise to not combine problems, XOSTOR is not completely bug free yet, so if you have an issue to report, get rid of XOSTOR in the equation first.
-
@olivierlambert Ok will do. Kubernetes is purely to learn .. so we good. Thank you
-
@Raymondello you right, the issue is from the storage and I am looking into that. Thank you for sharing the UAT Testing, I didn't know about it