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.

Commencez par reproduire des demandes de maintenance répétées sur un hôte KVM dans CloudStack 4.22.1.1, puis suivez le flux de migration de la VM de maintenance de l’hôte et la manière dont la liste des VM de l’hôte est mise à jour. La tâche est terminée lorsqu’une deuxième demande ignore les VM déjà migrées et que ces VM restent en fonctionnement au lieu d’être marquées comme arrêtées.

Rédigé par le modèle d'indexation à partir du texte de l'issue.