GitHub user weizhouapache added a comment to the discussion: Kubernetes cluster
deployment fails on new zone
> This is the significant fragement and it shows that the only host is not
> selected because of not enough capacity:
> ```
> 2025-02-26 13:14:40,198 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Work-Job-Executor-69:ctx-6947c681 job-114467/job-114470 ctx-f6b009cb
> FirstFitRoutingAllocator) (logid:a3c62ef8) Found 1 hosts for allocation after
> prioritization: [Host
> {"id":194,"name":"NODL1","type":"Routing","uuid":"cce73e3a-33f2-440a-8c50-f9133757b992"}]
> 2025-02-26 13:14:40,198 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Work-Job-Executor-69:ctx-6947c681 job-114467/job-114470 ctx-f6b009cb
> FirstFitRoutingAllocator) (logid:a3c62ef8) Looking for speed=500Mhz, Ram=256
> MB
> 2025-02-26 13:14:40,198 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Work-Job-Executor-69:ctx-6947c681 job-114467/job-114470 ctx-f6b009cb
> FirstFitRoutingAllocator) (logid:a3c62ef8) Host name: NODL1, hostId: 194 is
> in avoid set, skipping this and trying other available hosts
> 2025-02-26 13:14:40,198 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (Work-Job-Executor-69:ctx-6947c681 job-114467/job-114470 ctx-f6b009cb
> FirstFitRoutingAllocator) (logid:a3c62ef8) Host Allocator returning 0
> suitable hosts
> ```
> therefore the router is not deploy and hence the network is not started.
Yes
```
2025-02-26 13:14:39,679 ERROR [o.a.c.e.o.VolumeOrchestrator]
(Work-Job-Executor-69:ctx-6947c681 job-114467/job-114470 ctx-f6b009cb)
(logid:a3c62ef8) Unable to create volume [{"name":"R862995"}] due to
[com.cloud.utils.exception.CloudRuntimeException: Can't find
volume:6522397c-c425-47da-b1da-db36c99967cb.qcow2].
```
Looks like an issue with systemvm template.
How many secondary storages do you use ?
@tdtmusic2
GitHub link:
https://github.com/apache/cloudstack/discussions/10467#discussioncomment-12329019
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
