After removing a storage, replication states can still contain
references to it, even if no volume references it anymore.
If a storage does not exist in the storage configuration, the
replication target runs into an error when preparing the job locally.
This error prevents both running and removing the replication job. Fix
it by not passing the invalid storage ID in the first place.
Signed-off-by: Fiona Ebner <f.eb...@proxmox.com>
---
src/PVE/Replication.pm | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/PVE/Replication.pm b/src/PVE/Replication.pm
index 469ca19..bd627e5 100644
--- a/src/PVE/Replication.pm
+++ b/src/PVE/Replication.pm
@@ -275,6 +275,9 @@ sub replicate {
$logfunc->("guest => $guest_name, running => $running");
$logfunc->("volumes => " . join(',', @$sorted_volids));
+ # filter out left-over non-existing/removed storages - avoids error on
target
+ $state->{storeid_list} = [ grep { $storecfg->{ids}->{$_} }
$state->{storeid_list}->@* ];
+
if (my $remove_job = $jobcfg->{remove_job}) {
$logfunc->("start job removal - mode '${remove_job}'");
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
