ui: don't block offline migration due non-referenced disk in the config

All local disks can/will be migrated if not for a reason we don't
know about yet at this stage. The disks we get from the API call as
'local_disks' are either referenced by the config or by snapshots in
the config (which was not checked for and the reason one could run
into the 'else if' branch).

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.js
index cfc1316de7a476728fdac1222232ad82f2cf3e56..61bc6a492401ef0c213df472a0e70c41ade53193 100644 (file)
--- a/www/manager6/window/Migrate.js
+++ b/www/manager6/window/Migrate.js
@@ -265,13 +265,6 @@ Ext.define('PVE.window.Migrate', {
                                        severity: 'error'
                                    });
                                }
-
-                           } else if (!disk.referenced_in_config) {
-                               migration.possible = false;
-                               migration.preconditions.push({
-                                   text: 'Found not referenced/unused disk via storage: '+ disk.volid,
-                                   severity: 'error'
-                               });
                            } else {
                                migration['with-local-disks'] = 1;
                                migration.preconditions.push({