[
https://issues.apache.org/jira/browse/CLOUDSTACK-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Sorensen resolved CLOUDSTACK-2051.
-----------------------------------------
Resolution: Fixed
> KVM HA monitor sometimes remounts deleted storage pools
> -------------------------------------------------------
>
> Key: CLOUDSTACK-2051
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2051
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.1.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Fix For: 4.1.0
>
>
> I'm not sure if this is a race condition, a missing remove call, or what, but
> KVM HA monitor often remounts storage pools after they are deleted. The
> result is that every volume, snapsot, or template created can leave behind an
> orphaned NFS mountpoint. There have been other bugs fixed around this (unable
> to register storage pool in libvirt because pool is already mounted) that
> make the agent storage adaptors more robust, but this is one of the root
> causes.
> I've put together a fix that will allow the KVM HA Monitor to verify that an
> NFS pool in its list is valid (registered with libvirt, i.e. cloudstack knows
> about it) before going off and calling the script that mounts and performs HA
> on it.
--
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
