Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 30 Sep 2014 10:04:34 +0000 (UTC)
From: "Likitha Shetty (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12744896.1412067500000.154351.1412071474171@Atlassian.JIRA>
In-Reply-To: <JIRA.12744896.1412067500000@Atlassian.JIRA>
References: <JIRA.12744896.1412067500000@Atlassian.JIRA>
 <JIRA.12744896.1412067500978@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-7653) VM's are not getting deleted
 from hypervisor after deleting from UI when using zone wide primary storage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Likitha Shetty resolved CLOUDSTACK-7653.
----------------------------------------
    Resolution: Fixed

> VM's are not getting deleted from hypervisor after deleting from UI when using zone wide primary storage
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7653
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7653
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, VMware
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> +Root Cause Analysis+
> While expunging a volume, CS chooses the endpoint to perform delete operation on the hypervisor host by selecting any host that has the storage containing the volume mounted on it. In case of zone-wide primary storage since every host present in the zone will have the storage mounted a random will be chosen. But if it is not the host that is in the cluster that contains the VM, then the VM will not be deleted from the hypervisor.
> +Steps to reproduce+
> 1. Setup a VMware DC with 2 clusters and a zone-wide primary storage.
> 2. Deploy many VMs (since this issue will only be seen intermittently i.e. the random endpoint chosen doesn't contain the VM).
> 3. Call expunge for all VMs.
> 4. 1 or more VMs should still be present on the host in stopped state.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)