Retrying host maintenance falsely marks already-migrated VMs as stopped

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.

Empieza reproduciendo solicitudes de mantenimiento repetidas en un host KVM en CloudStack 4.22.1.1; después, sigue el flujo de migración de la VM de mantenimiento del host y cómo se actualiza la lista de VM del host. Se considera terminado cuando una segunda solicitud omite las VM que ya se migraron y esas VM permanecen en ejecución en lugar de marcarse como detenidas.

Escrito por el modelo de indexación a partir del texto del issue.