weizhouapache commented on issue #12920:
URL: https://github.com/apache/cloudstack/issues/12920#issuecomment-4161339188
@TimServers
I am able to reproduce the issue with ACS 4.22.0.0
2026-03-31 09:41:30,497 DEBUG [c.c.a.t.Request] (HA-Worker-3:[ctx-9f3e111f,
work-6049]) (logid:f0a26295) Seq 2-5905907961342989869: Sending { Cmd ,
MgmtId: 32988385510484, via: 2(ref-trl-10000-k-Mu24-wei-zhou-kvm2), Ver: v1,
Flags: 100011,
[{"com.cloud.agent.api.CheckVirtualMachineCommand":{"vmName":"i-2-400-VM","wait":"20","bypassHostMaintenance":"false"}}]
}
2026-03-31 09:41:30,539 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:[])
(logid:) Seq 2-5905907961342989869: Processing: { Ans: , MgmtId:
32988385510484, via: 2, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.CheckVirtualMachineAnswer":{"result":"false","details":"Domain
not found: no domain with matching name
'i-2-400-VM'","wait":"0","bypassHostMaintenance":"false"}}] }
2026-03-31 09:41:30,539 DEBUG [c.c.a.t.Request] (HA-Worker-3:[ctx-9f3e111f,
work-6049]) (logid:f0a26295) Seq 2-5905907961342989869: Received: { Ans: ,
MgmtId: 32988385510484, via: 2(ref-trl-10000-k-Mu24-wei-zhou-kvm2), Ver: v1,
Flags: 10, { CheckVirtualMachineAnswer } }
2026-03-31 09:41:30,540 DEBUG [c.c.h.CheckOnAgentInvestigator]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) Unable to get vm state
on VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
2026-03-31 09:41:30,540 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) SimpleInvestigator
could not find VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
2026-03-31 09:41:30,540 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) XenServerInvestigator
could not find VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
...
2026-03-31 09:41:30,735 DEBUG [c.c.h.KVMInvestigator]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) Neighbouring host:Host
{"id":1,"name":"ref-trl-10000-k-Mu24-wei-zhou-kvm1","type":"Routing","uuid":"d2eaf906-1533-4064-8699-e0d08376aee6"}
returned status:Up for the investigated host:Host
{"id":2,"name":"ref-trl-10000-k-Mu24-wei-zhou-kvm2","type":"Routing","uuid":"c04b6da8-7538-468a-bd1b-ae694dac1b23"}
2026-03-31 09:41:30,735 DEBUG [c.c.h.KVMInvestigator]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) HA: HOST is ineligible
legacy state Up for host Host
{"id":2,"name":"ref-trl-10000-k-Mu24-wei-zhou-kvm2","type":"Routing","uuid":"c04b6da8-7538-468a-bd1b-ae694dac1b23"}
2026-03-31 09:41:30,735 DEBUG [c.c.h.KVMInvestigator]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) HA: HOST is ineligible
legacy state Up for host Host
{"id":2,"name":"ref-trl-10000-k-Mu24-wei-zhou-kvm2","type":"Routing","uuid":"c04b6da8-7538-468a-bd1b-ae694dac1b23"}
2026-03-31 09:41:30,736 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) KVMInvestigator found
VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
to be alive? true
2026-03-31 09:41:30,736 DEBUG [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) VM VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
is found to be alive by KVMInvestigator
2026-03-31 09:41:30,736 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-9f3e111f, work-6049]) (logid:f0a26295) VM instance
{"id":400,"instanceName":"i-2-400-VM","state":"Running","type":"User","uuid":"56c59537-0315-4818-ad08-1df08b0da94d"}
is alive and host is up. No need to restart it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
