[
https://issues.apache.org/jira/browse/CLOUDSTACK-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619099#comment-13619099
]
Chip Childers commented on CLOUDSTACK-1846:
-------------------------------------------
Marcus,
I couldn't find a patch request for this, but I saw the request in the comments
above. I just applied the commit to the 4.1 branch. We should test this
against 4.1 and resolve (cut another bug for 4.0 if that fix is going to take
much longer).
commit eed4d2d92e44b5b308e6d395f7813f31215a3833
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 pools can silently fail to be unregistered, leading to failure
> to register later
> ----------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1846
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1846
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> 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 a placeholder, I have a fix.
> A specific deleteStoragePool method attempts to delete a libvirt storage
> pool, but failures are silently ignored (for example failure to unmount NFS
> pool because it's in use). Later, when pools are registered, they can fail to
> register because the mountpoint is in use. Part of my fix is to expose/log
> failures, and the other part is an attempt to handle the failures.
--
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
