Asadsid121 opened a new issue, #12239: URL: https://github.com/apache/cloudstack/issues/12239
### problem We have deployed the latest CloudStack version 4.22 in our test environment and are using Proxmox as the hypervisor. Earlier, we faced an issue where CloudStack always selected local-lvm on Proxmox instead of shared storage. That issue was resolved based on this previous discussion: https://github.com/apache/cloudstack/issues/12163 Now, after that fix, VMs are successfully created on the shared storage. However, we are facing a new problem: Issue: When we try to acquire an additional disk to a VM, CloudStack does not show any usable primary storage options for the Proxmox cluster. Details: When adding Primary Storage: If we select Scope: Cluster, the only storage option available is NFS If we select Scope: Zone and Hypervisor: Any, only NFS is shown. If we select Scope: Host or Scope: Cluster and choose Proxmox, CloudStack incorrectly shows XCP-ng hosts instead of Proxmox hosts. Impact: Because no primary storage can be properly added for Proxmox clusters, we are unable to acquire additional data disks for VMs. ### versions CloudStack: 4.22 Hypervisor: Proxmox VE 8.x Storage Type: (Shared Storage) Nodes in cluster: 2 Using Proxmox with CloudStack extension ### The steps to reproduce the bug ### What to do about it? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
