Details
Description
This is more of a placeholder, I have the fix.
When storage migration calls CopyVolumeCommand, it assumes that the primary storage has been used/registered before on the KVM host. It does something like a getStoragePool(poolUuid), and if primary storage pool (source or destination) has never been used on the host it will fail. The fix is simply to add the pool if it's not already there.