fix #3030: always activate volumes in storage_migrate
AFAICT the snapshot activation is not necessary for our plugins at the moment, but it doesn't really hurt and might be relevant in the future or for external plugins. Deactivating volumes is up to the caller, because for example, for replication on a running guest, we obviously don't want to deactivate volumes. Suggested-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
committed by
Thomas Lamprecht
parent
2c036838ed
commit
5324ceffef
@ -709,6 +709,13 @@ sub storage_migrate {
|
||||
};
|
||||
|
||||
volume_snapshot($cfg, $volid, $snapshot) if $migration_snapshot;
|
||||
|
||||
if (defined($snapshot)) {
|
||||
activate_volumes($cfg, [$volid], $snapshot);
|
||||
} else {
|
||||
activate_volumes($cfg, [$volid]);
|
||||
}
|
||||
|
||||
eval {
|
||||
if ($insecure) {
|
||||
my $input = IO::File->new();
|
||||
|
||||
Reference in New Issue
Block a user