GitHub user muthukrishnang1100 added a comment to the discussion: OOBM Issue during KVM HA
Yes, i tried to manually restart the failed host but, shows error <img width="432" height="271" alt="Screenshot 2026-01-07 114613" src="https://github.com/user-attachments/assets/0ce5eb37-e58e-4a79-800f-bb95a0374d48"; /> <img width="1577" height="287" alt="image" src="https://github.com/user-attachments/assets/dc241f5f-e1f4-47fc-87f6-163145bc48bb"; /> root@test-1:~# grep -i "Restart VM" /var/log/cloudstack/management/management-server.log 2026-01-07 06:27:50,718 WARN [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-4:ctx-7e914ac3 work-149) (logid:cdfe61be) Unable to restart VM instance {"id":54,"instanceName":"i-2-54-VM","state":"Stopped","type":"User","uuid":"aca1cc40-066c-4659-b768-b307f3f9bce7"} due to Unable to create a deployment for VM instance {"id":54,"instanceName":"i-2-54-VM","state":"Starting","type":"User","uuid":"aca1cc40-066c-4659-b768-b307f3f9bce7"} 2026-01-07 06:27:50,722 WARN [c.c.a.AlertManagerImpl] (HA-Worker-4:ctx-7e914ac3 work-149) (logid:cdfe61be) alertType=[8] dataCenterId=[3] podId=[3] clusterId=[null] message=[Unable to restart VM-07 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. 2026-01-07 06:27:50,727 WARN [c.c.a.AlertManagerImpl] (HA-Worker-4:ctx-7e914ac3 work-149) (logid:cdfe61be) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Unable to restart VM-07 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod] and content [Insufficient capacity to restart VM, name: VM-07, id: 54 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. 2026-01-07 06:27:50,774 WARN [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-3:ctx-cb5fcf36 work-146) (logid:4d03732c) Unable to restart VM instance {"id":45,"instanceName":"r-45-VM","state":"Stopped","type":"DomainRouter","uuid":"a2c09b9d-85c7-459b-bd75-a1051fa5284f"} due to Unable to create a deployment for VM instance {"id":45,"instanceName":"r-45-VM","state":"Starting","type":"DomainRouter","uuid":"a2c09b9d-85c7-459b-bd75-a1051fa5284f"} 2026-01-07 06:27:50,786 WARN [c.c.a.AlertManagerImpl] (HA-Worker-3:ctx-cb5fcf36 work-146) (logid:4d03732c) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Unable to restart r-45-VM which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod] and content [Insufficient capacity to restart VM, name: r-45-VM, id: 45 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. 2026-01-07 07:02:16,162 DEBUG [c.c.h.HighAvailabilityManagerImpl] (pool-4-thread-1:null) (logid:290274db) Notifying HA Mgr of to restart vm 45-r-45-VM 2026-01-07 07:02:16,175 DEBUG [c.c.h.HighAvailabilityManagerImpl] (pool-4-thread-1:null) (logid:290274db) Notifying HA Mgr of to restart vm 54-i-2-54-VM 2026-01-07 11:16:30,942 WARN [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-3:ctx-494e74cd work-166) (logid:10998aae) Unable to restart VM instance {"id":45,"instanceName":"r-45-VM","state":"Stopped","type":"DomainRouter","uuid":"a2c09b9d-85c7-459b-bd75-a1051fa5284f"} due to Unable to create a deployment for VM instance {"id":45,"instanceName":"r-45-VM","state":"Starting","type":"DomainRouter","uuid":"a2c09b9d-85c7-459b-bd75-a1051fa5284f"} 2026-01-07 11:16:30,952 WARN [c.c.a.AlertManagerImpl] (HA-Worker-3:ctx-494e74cd work-166) (logid:10998aae) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Unable to restart r-45-VM which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod] and content [Insufficient capacity to restart VM, name: r-45-VM, id: 45 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. 2026-01-07 11:55:33,903 WARN [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-1:ctx-2e27fa35 work-169) (logid:8fdc4e5e) Unable to restart VM instance {"id":54,"instanceName":"i-2-54-VM","state":"Stopped","type":"User","uuid":"aca1cc40-066c-4659-b768-b307f3f9bce7"} due to Unable to create a deployment for VM instance {"id":54,"instanceName":"i-2-54-VM","state":"Starting","type":"User","uuid":"aca1cc40-066c-4659-b768-b307f3f9bce7"} 2026-01-07 11:55:33,907 WARN [c.c.a.AlertManagerImpl] (HA-Worker-1:ctx-2e27fa35 work-169) (logid:8fdc4e5e) alertType=[8] dataCenterId=[3] podId=[3] clusterId=[null] message=[Unable to restart VM-07 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. 2026-01-07 11:55:33,915 WARN [c.c.a.AlertManagerImpl] (HA-Worker-1:ctx-2e27fa35 work-169) (logid:8fdc4e5e) No recipients set in global setting 'alert.email.addresses', skipping sending alert with subject [Unable to restart VM-07 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod] and content [Insufficient capacity to restart VM, name: VM-07, id: 54 which was running on host name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod]. root@test-1:~# but, it comes error like this something is blocked. but< HA is working VM only still not auto started and also if itried to manually started error. GitHub link: https://github.com/apache/cloudstack/discussions/12353#discussioncomment-15433985 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
