-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
ISSUE TYPE
- Bug Report
VERSION
- CloudStack 4.20.1.0
- MariaDB Galera 15.1 Distrib 10.5.27-MariaDB, for Linux (x86_64) using EditLine wrapper
- ceph version 19.2.3 (c92aebb279828e9c3c1f5d24613efca272649e62) squid (stable)
OS / ENVIRONMENT
- Rocky Linux 9.6
CONFIGURATION
- 1 Mgmt
- 2 Hypervisor KVM
Normal CloudStack configuration according to documentation
Advanced networking with 4 Network Interfaces:
Cloudbr0 → Management (LAN)
Cloudbr1 → Public (WAN)
Cloudbr2 → Guest
Cloudbr3 → StoragePrimary Storage: RBD (Ceph) pool cloudstack
Secondary Storage: RGW S3 (Ceph) bucket cloudstack
Issue:
The following virtual machines fail to deploy:
v-3-VM
s-4-VMThey cannot be created because the system reports insufficient capacity to deploy the VM:
2025-09-05 14:10:29,334 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-9:[ctx-5b3cf25c, job-3/job-159, ctx-75f60b19]) (logid:2f8eebb8) Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {"id":3,"instanceName":"v-3-VM","state":"Starting","type":"ConsoleProxy","uuid":"855516ca-9e46-420e-9c6a-c92c9ad32eb5"}Scope=interface com.cloud.dc.DataCenter; id=3
2025-09-05 14:10:29,334 INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-9:[ctx-5b3cf25c, job-3/job-159, ctx-75f60b19]) (logid:2f8eebb8) Rethrow exception com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {"id":3,"instanceName":"v-3-VM","state":"Starting","type":"ConsoleProxy","uuid":"855516ca-9e46-420e-9c6a-c92c9ad32eb5"}Scope=interface com.cloud.dc.DataCenter; id=3
There is capacity in the primary storage and in the hypervisors to be able to deploy the virtual machines, so the problem does not lie in that.
I previously made a similar installation, but instead of ceph for primary and secondary storage, I used a TrueNAS NFS, there I have no problem, so perhaps the problem may lie in the Primary Storage, since Cloudstack is able to download the template and store it in the Secondary Storage (Bucket), but cloudstack recognizes the capabilities of the primary storage, so I am in doubt and I cannot understand what is wrong.

I attach a more extended log file