GitHub user kiranchavala added a comment to the discussion: VM HA not working 
when there's an issue with vm restart

@gusmef 

I had introduced the kernel panic with the following command "echo c > 
/proc/sysrq-trigger"

The kvm host went to alert state  and no ha entry was created for the vm under 
"select * from op_ha_work"

<img width="1463" height="187" alt="Image" 
src="https://github.com/user-attachments/assets/cebf6d24-f48e-4844-9e62-91733916b0be";
 />

```
2026-06-29 12:34:09,322 INFO  [c.c.a.m.ClusteredAgentManagerImpl] 
(AgentTaskPool-1:[ctx-14c00e81]) (logid:d84d661c) The agent from host Host 
{"id":1,"name":"Cloudstack-Kvm-Host1","type":"Routing","uuid":"c3b12744-eaa4-44db-b261-3b548fbfb49b"}
 state determined is Disconnected
2026-06-29 12:34:09,322 WARN  [c.c.a.m.ClusteredAgentManagerImpl] 
(AgentTaskPool-1:[ctx-14c00e81]) (logid:d84d661c) Agent is disconnected but the 
host is still up: Host 
{"id":1,"name":"Cloudstack-Kvm-Host1","type":"Routing","uuid":"c3b12744-eaa4-44db-b261-3b548fbfb49b"}
 state: Enabled
2026-06-29 12:34:09,333 WARN  [c.c.a.AlertManagerImpl] 
(AgentTaskPool-1:[ctx-14c00e81]) (logid:d84d661c) No recipients set in global 
setting 'alert.email.addresses', skipping sending alert with subject [Host 
disconnected, name: Cloudstack-Kvm-Host1 
(id:c3b12744-eaa4-44db-b261-3b548fbfb49b), availability zone: 
kiran-home-lab-zone1, pod: pod1] and content [If the agent for host [name: 
Cloudstack-Kvm-Host1 (id:c3b12744-eaa4-44db-b261-3b548fbfb49b), availability 
zone: kiran-home-lab-zone1, pod: pod1] is not restarted within alert.wait 
seconds, host will go to Alert state].
2026-06-29 12:34:09,334 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(AgentTaskPool-1:[ctx-14c00e81]) (logid:d84d661c) Deregistering link for 
AgentAttache 
{"_id":1,"_name":"Cloudstack-Kvm-Host1","_uuid":"c3b12744-eaa4-44db-b261-3b548fbfb49b"}
 with state Alert

```



With  the  fix https://github.com/apache/cloudstack/pull/13373

The host goes into down state and the vm ha is triggered 

Could you please provide the command you used to trigger the kernel panic 

and also the values of the global settings 

```

"commands.timeout" = 


```






GitHub link: 
https://github.com/apache/cloudstack/discussions/13729#discussioncomment-17810555

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to