[pve-devel] [PATCH manager 3/3] Don't block offline migration when a disk is not referenced in the current config

Fabian Ebner f.ebner at proxmox.com
Thu Apr 16 14:54:44 CEST 2020


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 at proxmox.com>
---

Does not depend on the other patches.

 www/manager6/window/Migrate.js | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.js
index cfc1316d..61bc6a49 100644
--- 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({
-- 
2.20.1





More information about the pve-devel mailing list