[
https://issues.apache.org/jira/browse/CLOUDSTACK-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617923#comment-13617923
]
Marcus Sorensen commented on CLOUDSTACK-1845:
---------------------------------------------
commit 5a16e70de9d7bfd93f71bf476de8e23f84e52152
Author: Marcus Sorensen <[email protected]>
Date: Fri Mar 29 18:31:26 2013 -0600
CLOUDSTACK-1846, CLOUDSTACK-1845 - KVM Storage, sometimes KVMHA will remount
deleted NFS pools, causing failures when defining new storage pools.
Sometimes
a storage pool has never been used on a host, and getStoragePool fails when
copying templates or in storage migration. deleteStoragePool(pool) often
fails
silently, leaving no pool defined in libvirt, but a mountpoint left behind.
This patch handles some of these exceptions and brings forward any issues
via
logging.
Signed-off-by: Marcus Sorensen <[email protected]> 1364603486 -0600
> 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
