GitHub user ShadowJonathan edited a discussion: Encountered issues when attempting to bootstrap CloudStack with Proxmox
Here are a few things I encountered while attempting to install/add Proxmox to cloudstack; I started using Debian 13, the latest, considering that some/most things would work well on it. However, there's no `.deb`s for trixie, which I already addressed here: #12251 Then, when using debian 12's `.deb`s, I encountered #12252 in that there's no documentation stating this repository needed to be added. Furthermore, debian 13 is also not supported in that repository, it seems. Installing the connector manually (which worked), I finally got cloudstack properly setup. Going through the setup (`cloudstack-setup-databases`, `cloudstack-setup-management`) was also no issue. I then attempted to install a new zone, with the following zone-wide settings: <img width="1070" height="828" alt="image" src="https://github.com/user-attachments/assets/f52955bb-3d0c-430c-87aa-d7fad6e3f731"; /> I could only select "external", not proxmox or the likes. Then, when arriving at the step to add a cluster with a host, I was met with mostly blank pages: <img width="1070" height="641" alt="image" src="https://github.com/user-attachments/assets/eb917e59-4f55-4c61-b2d7-3703ed87925a"; /> <img width="1068" height="685" alt="image" src="https://github.com/user-attachments/assets/653a5ac9-9545-4b00-911e-fc2ca2b71795"; /> <img width="1062" height="660" alt="image" src="https://github.com/user-attachments/assets/d1622c99-8f85-4bee-99e8-b1f270bd3cb8"; /> Then, when launching the wizard, it fails on this page: <img width="1062" height="939" alt="image" src="https://github.com/user-attachments/assets/daaf8846-0528-4a8f-b8e3-0f8b27d53697"; /> Which, after some debugging, is a client-side error here: https://github.com/apache/cloudstack/blob/53a39d3ff7967886c91ee51a297b26cabfa57b21/ui/src/views/infra/zone/ZoneWizardLaunchZone.vue#L1366 (`indexOf` seems to be a JS client error) --- Continuing, I go install secondary storage. I had to remove the added cluster because it wasn't configured with the right proxmox settings, and I couldn't add a proxmox host. So I install the host following [this documentation](https://docs.cloudstack.apache.org/en/latest/adminguide/extensions/inbuilt_extensions.html#proxmox) When I try to add primary storage, I get the following error message: <img width="394" height="243" alt="image" src="https://github.com/user-attachments/assets/bd8aa181-a374-4090-9c2a-a76328cc9005"; /> Which is because of this part in the proxmox.sh file: https://github.com/apache/cloudstack/blob/71f47d61304d1a05627bc335c8d35d7ef1040fe1/extensions/Proxmox/proxmox.sh#L63 I skip primary storage, as it seems I can't add this, or that it's configured in some other way. I add a template, to test launch a VM: <img width="617" height="1342" alt="image" src="https://github.com/user-attachments/assets/ebf00fca-bae0-4f5f-9e92-fd3f66bb5844"; /> That works, then I try to create an instance from it, which fails with this: <img width="389" height="164" alt="image" src="https://github.com/user-attachments/assets/9052ef4c-4cd7-4084-8216-8609ecd874f3"; /> I try to run it again, specifying the host, but this time it fails again: <img width="398" height="165" alt="image" src="https://github.com/user-attachments/assets/53f25437-a315-4b54-be4c-7617461e2f43"; /> I realise the zone was disabled, enable it, and recreate the VM, which gets me this error: <img width="399" height="162" alt="image" src="https://github.com/user-attachments/assets/ddfa9721-0739-4ac3-8f8f-90c3c6d3bf73"; /> Looking at the logs, it gives me this: ``` 2025-12-16 18:18:29,159 ERROR [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-10:[ctx-ca2a9424, job-49/job-51, ctx-8cb0346d]) (logid:ce949871) Unable to orchestrate start VM instance {"id":3,"instanceName":"i-2-3VM","state":"Stopped","type":"User","uuid":"53f4a94c-3124-4368-952e-7da10c9f472f"} due to [Cannot find an available cluster in Pod 2 to start domain router for Ovm. Ovm won't support any system vm including domain router, please make sure you have a cluster with hypervisor type of any of xenserver/KVM/Vmware in the same pod with Ovm cluster. And there is at least one host in UP status in that cluster.]. ``` Which is where I'll leave it for now, as this seems to be a proper blocker. GitHub link: https://github.com/apache/cloudstack/discussions/12273 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
