Damans227 opened a new issue, #14026: URL: https://github.com/apache/cloudstack/issues/14026
CLOUDSTACK VERSION 4.22.1.1, KVM hypervisor SUMMARY Putting a host into maintenance moves its VMs off one at a time, which can take a while. Requesting maintenance again on the same host before the first request finishes causes it to retry moving every VM still listed against that host, including ones already moved. That retry fails as expected, but for some VMs it confuses CloudStack into thinking the VM was powered off, and it gets marked stopped even though it was never touched and kept running the whole time. EXPECTED Requesting maintenance again should not retry VMs already moved. ACTUAL Some already-moved VMs get falsely marked stopped. NOTE The false "stopped" status seems to come from CloudStack losing track of which VMs are on which host. That could plausibly happen from causes other than this one, but we only have evidence of it via this scenario. -- 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]
