GitHub user yann1ck-oder-so edited a comment on the discussion: System VMs fail 
to start – “Unable to create a deployment for VM instance

Is this more usefull?

```java
2025-10-24 06:51:38,464 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) 
Publish async job-2298 complete on message bus
2025-10-24 06:51:38,464 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) Wake 
up jobs related to job-2298
2025-10-24 06:51:38,464 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) Update 
db status for job-2298
2025-10-24 06:51:38,465 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) Wake 
up jobs joined with job-2298 and disjoin all subjobs created from job- 2298
2025-10-24 06:51:38,473 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl$5] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) Done 
executing com.cloud.vm.VmWorkStart for job-2298
2025-10-24 06:51:38,473 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid:9ca0f174) Remove 
job-2298 from job monitoring
2025-10-24 06:51:38,481 WARN  [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:[ctx-78241083]) (logid:8d474bb9) Unable to start proxy [874] 
due to [Unable to create a deployment for VM instance 
{"id":874,"instanceName":"v-874-VM","state":"Starting","type":"ConsoleProxy","uuid":"5856057e-97e7-41f9-90f7-e524d6a661f9"}].
 com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
deployment for VM instance 
{"id":874,"instanceName":"v-874-VM","state":"Starting","type":"ConsoleProxy","uuid":"5856057e-97e7-41f9-90f7-e524d6a661f9"}Scope=interface
 com.cloud.dc.DataCenter; id=1
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1451)
        at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5827)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:102)
        at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5951)
        at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:689)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
        at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:637)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
```


GitHub link: 
https://github.com/apache/cloudstack/discussions/11903#discussioncomment-14769517

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to