Dominik Csapak 1aa4d844a1 ReplicationState: purge state from non local vms ... when running replication, we don't want to keep replication states for non-local vms. Normally this would not be a problem, since on migration, we transfer the states anyway, but when the ha-manager steals a vm, it cannot do that. In that case, having an old state lying around is harmful, since the code does not expect the state to be out-of-sync with the actual snapshots on disk. One such problem is the following: Replicate vm 100 from node A to node B and C, and activate HA. When node A dies, it will be relocated to e.g. node B and start replicate from there. If node B now had an old state lying around for it's sync to node C, it might delete the common base snapshots of B and C and cannot sync again. Deleting the state for all non local guests fixes that issue, since it always starts fresh, and the potentially existing old state cannot be valid anyway since we just relocated the vm here (from a dead node). Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> Reviewed-by: Fabian Ebner <f.ebner@proxmox.com>		2022-06-08 08:48:04 +02:00
debian	bump version to 4.1-2	2022-04-27 18:51:21 +02:00
src	ReplicationState: purge state from non local vms	2022-06-08 08:48:04 +02:00
Makefile	build: switch upload target to bullseye	2021-06-09 11:39:15 +02:00