The logs from KVM host attached: 2023-04-05 16:44:51,323 WARN [kvm.resource.KVMHAChecker] (pool-44539-thread-1:null) (logid:8a3b6d5e) All checks with KVMHAChecker for host IP [10.220.65.112] in pools [] considered it as dead. It may cause a shutdown of the host. 2023-04-05 16:44:52,398 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) (logid:76198124) Trying to fetch storage pool ffeb7f34-f4de-4fcc-ab08-1bac4d31342b from libvirt 2023-04-05 16:44:52,414 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) (logid:76198124) Asking libvirt to refresh storage pool ffeb7f34-f4de-4fcc-ab08-1bac4d31342b 2023-04-05 16:44:52,456 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) (logid:76198124) Trying to fetch storage pool 279990a5-1ada-475f-a068-6dbc0f6c53b9 from libvirt 2023-04-05 16:44:52,460 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) (logid:76198124) Asking libvirt to refresh storage pool 279990a5-1ada-475f-a068-6dbc0f6c53b9 2023-04-05 16:44:55,250 WARN [kvm.resource.KVMHAChecker] (pool-44540-thread-1:null) (logid:8a81957c) All checks with KVMHAChecker for host IP [10.220.65.111] in pools [] considered it as dead. It may cause a shutdown of the host. 2023-04-05 16:44:55,348 WARN [kvm.resource.KVMHAChecker] (pool-44541-thread-1:null) (logid:9b33c350) All checks with KVMHAChecker for host IP [10.220.65.112] in pools [] considered it as dead. It may cause a shutdown of the host. 2023-04-05 16:44:59,278 WARN [kvm.resource.KVMHAChecker] (pool-44542-thread-1:null) (logid:099e8960) All checks with KVMHAChecker for host IP [10.220.65.111] in pools [] considered it as dead. It may cause a shutdown of the host. 2023-04-05 16:44:59,387 WARN [kvm.resource.KVMHAChecker] (pool-44544-thread-1:null) (logid:d0f70020) All checks with KVMHAChecker for host IP [10.220.65.112] in pools [] considered it as dead. It may cause a shutdown of the host.
Regards, Jafar Aghabalayev -----Original Message----- From: Jafar Aghabalayev <[email protected]> Sent: Thursday, April 6, 2023 12:38 AM To: [email protected] Subject: RE: Failed to create VPC I try to delete host tag and it works now. When I add the host tag VPC couldn't create Also I noticed that HA state is degraded. Look like the issue related to HA state Regards, Jafar Aghabalayev -----Original Message----- From: Jafar Aghabalayev <[email protected]> Sent: Thursday, April 6, 2023 12:30 AM To: [email protected] Subject: RE: Failed to create VPC Hello, Yes, the primary storage is sharedmountpoint and it run correctly as I can create VMs within the primary storage. The template properly registered, as I can use system VMs (secondary storage and console proxy). Also I try to delete template and readd it again. I have one cluster and the resource usage from GUI attached and output from DB attached on previous email. Regards, Jafar Aghabalayev -----Original Message----- From: Nux <[email protected]> Sent: Wednesday, April 5, 2023 6:45 PM To: [email protected] Subject: Re: Failed to create VPC This seems to indicate that there is no CPU or RAM available. Can you double check? Also have a look for the obvious, is the primary storage running correctly, secondary storage same, are the templates properly registered etc etc. Checking resources in Cluster: 1 under Pod: 1 ) (logid:4d0b3a74) Guest VM is requested with Custom[UEFI] Boot Type false ) (logid:4d0b3a74) Looking for hosts in dc: 1 pod:1 cluster:1 ) (logid:4d0b3a74) FirstFitAllocator has 0 hosts to check for allocation: [] ) (logid:4d0b3a74) Found 0 hosts for allocation after prioritization: [] ) (logid:4d0b3a74) Looking for speed=500Mhz, Ram=256 MB ) (logid:4d0b3a74) Host Allocator returning 0 suitable hosts No suitable hosts found No suitable hosts found under this Cluster: 1 On 2023-04-04 20:28, Jafar Aghabalayev wrote: > Hello Nux, > > The logs uploaded: > https://gist.github.com/jaghabalayev/3f21d245a686c8a2049ef146f0fe7113 > > Regards, > > > > Jafar Aghabalayev > > -----Original Message----- > From: Nux <[email protected]> > Sent: Tuesday, April 4, 2023 6:38 PM > To: [email protected] > Cc: Jafar Aghabalayev <[email protected]> > Subject: Re: Failed to create VPC > > Hello, > > It doesn't seem able to spawn the virtual router. Likely the cause is > listed earlier in the logs. > Please set your logs to DEBUG and try again, sending much more logs - > perhaps use a pastebin service. > > > On 2023-04-04 15:26, Jafar Aghabalayev wrote: >> Hello Community, >> >> I try to create VPC, but it failed. However, I can create VMs with no >> problem. Both system VMs are in up state. >> >> The full logs from management server are attached. During of VPC >> deployment I found the below log: >> >> 2023-04-04 09:37:02,447 WARN [c.c.n.v.VpcManagerImpl] >> (API-Job-Executor-58:ctx-3c1c4569 job-4058 ctx-850b8a44) >> (logid:4d0b3a74) Failed to start vpc [VPC [11-vpc-pt] due to >> >> com.cloud.exception.InsufficientServerCapacityException: Unable to >> create a deployment for VM instance {id: "1148", name: "r-1148-VM", >> uuid: "c7071b4e-c1d7-4ae9-bda5-840ffb2b678a", >> type="DomainRouter"}Scope=interface com.cloud.dc.DataCenter; id=1 >> >> Additionally, the output from cloud.vm_instance, cloud.host, >> cloud.cluster, cloud.usage_event tables attached. >> >> Appreciate any kind of support. >> >> Regards, >> >> Jafar Aghabalayev
