Enforce that affected storages are enabled and have the correct content type
before doing a migration. And only pick up unreferenced guest volumes from
storages that support the content type.
Can be considered a breaking change, but it'll only affect scenarios where there
is a guest's volume on a misconfigured storage, so it can also be considered a
bug fix. Still, best to do it for a major release.
Another small change regarding misconfigured 'none' content type is thrown in,
patches storage #2 and manager #2, which also should rather be done for a major
release.
Dependency-wise, only patch storage #1 is relevant, as it breaks older migration
code, but should also be limited to scenarios with unused/unreferenced/vmstate
local disks *and* misconfigured storage.
pve-container:
Fabian Ebner (3):
prefer storage_check_enabled over storage_check_node
migrate: also test unused volumes
migrate: enforce that rootdir content type is available
qemu-server:
Fabian Ebner (2):
prefer storage_check_enabled over storage_check_node
migrate: enforce that image content type is available
PVE/API2/Qemu.pm | 4 ++--
PVE/QemuMigrate.pm | 31 +++++++++++++++++++------------
PVE/QemuServer.pm | 7 +++++--
3 files changed, 26 insertions(+), 16 deletions(-)
pve-storage:
Fabian Ebner (2):
vdisk_list: only scan storages with the correct content type(s)
config: prevent empty content list when content type 'none' is not
supported
PVE/Storage.pm | 8 ++------
PVE/Storage/Plugin.pm | 4 ++++
2 files changed, 6 insertions(+), 6 deletions(-)
pve-manager:
Fabian Ebner (2):
pve6to7: add check for guest images on misconfigured storages
pve6to7: check for misconfigured content type 'none'
PVE/CLI/pve6to7.pm | 50 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
--
2.20.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
