You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/04/24 23:21:16 UTC
[jira] [Commented] (CLOUDSTACK-2173) template/volume cleanup fails
when KVM HA monitor is used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640969#comment-13640969 ]
ASF subversion and git services commented on CLOUDSTACK-2173:
-------------------------------------------------------------
Commit 7fa57922a40428d73e80f5f2a48ff67c8cecd148 in branch refs/heads/master from Marcus Sorensen <ma...@betterservers.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7fa5792 ]
Detail: Delete KVMHA dir contents if found when deleting templates, volumes
from Nfs Secondary storage
BUG-ID: CLOUDSTACK-2173
Bugfix-for: 4.2
Signed-off-by: Marcus Sorensen <ma...@betterservers.com> 1366838425 -0600
> template/volume cleanup fails when KVM HA monitor is used
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-2173
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2173
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Fix For: 4.1.0, 4.2.0
>
>
> the KVM HA runner uses any NFS secondary storage resource available to a host to store it's HA data. This causes template deletes to fail because it cannot delete KVMHA, which is a directory that is not empty.
> 2013-04-24 15:04:13,724 DEBUG [agent.manager.AgentManagerImpl] (StorageManager-Scavenger-1:null) Details from executing class com.cloud.agent.api.storage.DeleteTemplateCommand: Unable to delete file KVMHA under Template path template/tmpl/2/205//56675860-3040-36f4-95c2-4115336f7c1a.qcow2
--
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