cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1846) KVM - storage pools can silently fail to be unregistered, leading to failure to register later
Date Sat, 30 Mar 2013 00:35:16 GMT


ASF subversion and git services commented on CLOUDSTACK-1846:

Commit 5a16e70de9d7bfd93f71bf476de8e23f84e52152 in branch refs/heads/master from Marcus Sorensen
[;h=5a16e70 ]

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

Signed-off-by: Marcus Sorensen <> 1364603486 -0600

> KVM - storage pools can silently fail to be unregistered, leading to failure to register
> ----------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-1846
>                 URL:
>             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:

View raw message