GitHub user muthukrishnang1100 added a comment to the discussion: OOBM Issue
during KVM HA
When I tried to test VM HA only, this error is come, But, we have all 3 hosts
more than available capacity and also all 3 hosts VMs we use low offerings.
but, still this error is comes
2026-01-09 13:39:18,165 DEBUG [c.c.a.t.Request]
(RouterStatusMonitor-1:ctx-11ea2d26) (logid:1cb3b8a6) Seq
3-3771201737969370277: Sending { Cmd , MgmtId: 270790104347868, via: 3(test-2),
Ver: v1, Flags: 100011,
[{"com.cloud.agent.api.routing.SetMonitorServiceCommand":{"healthChecksConfig":{"gateways":"gatewaysIps=169.254.0.1
192.168.150.1
","portForwarding":"","systemThresholds":"minDiskNeeded=100.0,maxCpuUsage=100.0,maxMemoryUsage=100.0;","haproxyData":"","virtualMachines":"vmName=VM-01,macAddress=02:03:00:d2:00:1e,ip=10.0.1.194,dhcp=true,dns=true;vmName=VM-02,macAddress=02:03:00:d3:00:0d,ip=10.0.2.106,dhcp=true,dns=true;vmName=VM-03,macAddress=02:03:00:d4:00:0e,ip=10.0.3.95,dhcp=true,dns=true;","routerVersion":"templateVersion=Cloudstack
Release 4.19.1 Mon 08 Jul 2024 08:19:20 AM
UTC,scriptsVersion=d0105cf631550faa80b21f6d5c10b833
2026-01-09 13:39:20,581 DEBUG [c.c.a.t.Request]
(RouterStatusMonitor-1:ctx-11ea2d26) (logid:1cb3b8a6) Seq
2-4431260558355858861: Sending { Cmd , MgmtId: 270790104347868, via: 2(test-1),
Ver: v1, Flags: 100011,
[{"com.cloud.agent.api.routing.SetMonitorServiceCommand":{"healthChecksConfig":{"gateways":"gatewaysIps=169.254.0.1
192.168.150.1
","portForwarding":"","systemThresholds":"minDiskNeeded=100.0,maxCpuUsage=100.0,maxMemoryUsage=100.0;","haproxyData":"","virtualMachines":"vmName=VM-01,macAddress=02:03:00:d2:00:1e,ip=10.0.1.194,dhcp=true,dns=true;vmName=VM-02,macAddress=02:03:00:d3:00:0d,ip=10.0.2.106,dhcp=true,dns=true;vmName=VM-03,macAddress=02:03:00:d4:00:0e,ip=10.0.3.95,dhcp=true,dns=true;","routerVersion":"templateVersion=Cloudstack
Release 4.19.1 Mon 08 Jul 2024 08:19:20 AM
UTC,scriptsVersion=d0105cf631550faa80b21f6d5c10b833
2026-01-09 13:39:38,568 WARN [c.c.a.AlertManagerImpl]
(AgentTaskPool-8:ctx-327985c9) (logid:fc064230) No recipients set in global
setting 'alert.email.addresses', skipping sending alert with subject [Host is
down, name: test-3 (id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod] and
content [Host [name: test-3 (id:6), availability zone: Xaasio-Zone, pod:
Xaasio-Pod] is down. Starting HA on the following VMs: VM-03].
2026-01-09 13:39:47,870 DEBUG [c.c.h.Ovm3Investigator]
(HA-Worker-3:ctx-a94907bf work-239) (logid:beead11f) isVmAlive: VM-03 on test-3
2026-01-09 13:39:57,111 WARN [c.c.a.AlertManagerImpl] (HA-Worker-3:ctx-a94907bf
work-239) (logid:beead11f) alertType=[8] dataCenterId=[3] podId=[3]
clusterId=[null] message=[Unable to restart VM-03 which was running on host
name: test-3(id:6), availability zone: Xaasio-Zone, pod: Xaasio-Pod].
2026-01-09 13:39:57,115 WARN [c.c.a.AlertManagerImpl] (HA-Worker-3:ctx-a94907bf
work-239) (logid:beead11f) No recipients set in global setting
'alert.email.addresses', skipping sending alert with subject [Unable to restart
VM-03 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-03, id: 92 which was running on host name: test-3(id:6), availability
zone: Xaasio-Zone, pod: Xaasio-Pod].
GitHub link:
https://github.com/apache/cloudstack/discussions/12353#discussioncomment-15454971
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
