edikevich

Hi. Sorry for delay. I didn't test this feature in 4.15.2 :( I think problem is near Affinity group which is created after dedicate host/cluster/pod. I tried create VM from...

Hi. Not exactly. When pod is dedicated affinity group is created automatically by CS. Other steps are correct.

Hi. I don't have any errors in log. I see only that no suitable hosts found.

Sorry. Have Error: 2022-01-12 12:42:14,559 INFO [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-17:ctx-10e86d4b job-3810 ctx-ed36cebb) (logid:7ebaa05f) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {id: "334", name: "i-34-334-VM", uuid: "88d9976d-0b1a-4c78-a201-b6d153cf0e58", type="User"}Scope=interface com.cloud.dc.DataCenter; id=1 2022-01-12...

2022-01-12 12:42:14,354 INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-17:ctx-10e86d4b job-3810) (logid:0d4e47c6) Add job-3810 into job monitoring 2022-01-12 12:42:14,358 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (qtp239372207-1931187:ctx-e0fcca0e ctx-b49fa34b) (logid:ccaa1505) submit async job-3810, details: AsyncJobVO {id:3810, userId: 37, accountId: 34, instanceType:...

I have dedicated pod in my environment  I created offering without tag before and had same result

All our pods have different CIDRs. But all out hypervisords can see Management server. When I release dedicated Pod I can deploy VMs in this Pod.

Log when Compute Offering don't contains any tags ``` 2022-01-12 17:14:30,364 INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-24:ctx-3fefa540 job-3832) (logid:85ae8d9d) Add job-3832 into job monitoring 2022-01-12 17:14:30,368 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (qtp239372207-1939856:ctx-5eab9574 ctx-c6dff037) (logid:c28fe315) submit async...

Can I ask you? When we dedicated Pod something change in host_pod_ref?

Where in DB I can see dedication?