[ https://issues.apache.org/jira/browse/CLOUDSTACK-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chip Childers resolved CLOUDSTACK-1845. --------------------------------------- Resolution: Fixed this has been applied to 4.0, master and 4.1 branches > KVM - storage migration often fails > ----------------------------------- > > Key: CLOUDSTACK-1845 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1845 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.0.2, 4.1.0, 4.2.0 > Reporter: Marcus Sorensen > Assignee: Marcus Sorensen > Priority: Critical > Fix For: 4.0.2, 4.1.0, 4.2.0 > > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira