catborise 5061cc7f2c fix(instances): a migration runs in the mode the VM's state allows, and is logged as it ran ... moveto read the VM state for each flag and dropped options that did not fit it, so a request could run as something else than asked; the log then named the mode from the form ("live" or "offline"), not the one used. The API did not log at all and answered "instance migrate is started" after the migration had finished. - moveto reads the state once. A running VM migrates live, or without live paused for the transfer (non-live); a paused VM stays paused; a shut-off VM moves offline. Live for a shut-off VM, offline for a running or paused one, and any other state are refused before anything changes. unsafe, auto converge (live only) and compressed apply to a running VM. - migrate_instance logs the outcome for the VM page and the API: the mode and options used, or the error. The API answers "instance is migrated (<mode>)" and accepts requests that leave out an optional option. - Post copy is gone from the form, the view and the API: only the flag was set, and without migrateStartPostCopy, which the app never called, the migration never switched to post copy.		2026-10-06 15:26:49 +03:00
..
serializers.py	fix(instances): a migration runs in the mode the VM's state allows, and is logged as it ran	2026-10-06 15:26:49 +03:00
viewsets.py	fix(instances): a migration runs in the mode the VM's state allows, and is logged as it ran	2026-10-06 15:26:49 +03:00