BartJM commented on issue #11286: URL: https://github.com/apache/cloudstack/issues/11286#issuecomment-3140031992
I had not considered ntp issues, but we keep sync with chrony, so not expecting that to be an issue. I think the cause is related to the multiple async maintenance jobs, since the stopped vms were not originally on Host A. I however expect that cancelling the maintenance and having the enabled state on the hypervisor does not start migrations due to a still present async job. The main issue however is that the vm was stopped by Cloudstack after the migration to the host in maintenance failed. Currently I do not have much time to further investigate, but if there are specific places in the db (or elsewhere) to look I will be able to check. Sadly was still not able to reproduce. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
