Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of ilya.mailing.lists@gmail.com
 designates 209.85.192.169 as permitted sender)
Message-ID: <5509D789.7000306@gmail.com>
Date: Wed, 18 Mar 2015 12:52:41 -0700
From: ilya <ilya.mailing.lists@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dev@cloudstack.apache.org
Subject: Re: BUG: anybody addressing this one ?
References: 
 <CAMvtBPMA0ORfFPxEFfMbeoQnL1jOT-fxuEC9pCHWH08Z6PEDhw@mail.gmail.com>
In-Reply-To: 
 <CAMvtBPMA0ORfFPxEFfMbeoQnL1jOT-fxuEC9pCHWH08Z6PEDhw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

It looks like we have 2 issues here.

1) you are seeing volumes you should not see

2) volume purging is not implemented

There are several solution to #2

1) I've written a shell script that deletes all volumes that are in 
detached state for over X number of days. I'll see if i can share the 
script. This could be temporary solution run as cronjob periodically.

2) Marcus has written an API extension call that will delete the VM with 
volumes, slightly different API call needs to be invoked, something like 
destroyVmWithVolumes, the volumes will be expunged at the same time as 
VM. Its not part of the cloudstack UI, but could be integrated - hoping 
someone with UI experience can do that. The code will be committed 
upstream hopefully soon, there is some internal delay for releasing 
that, but we will work this through.


On 3/18/15 4:58 AM, Andrija Panic wrote:
> Hi,
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-7926
>
> Currently I have hit a bug, when I click on some instance, then on View
> Volumes, and then I get listed volumes that belong to some other VM - it
> already happened to me that I deleted the volumes - beacuse of ACS bug in
> GUI !
>
> So, I suggest to consider maybe to implement purging volumes the same way
> it is implemented with VM-s - so the VM is not really deleted - and the
> purge thread in ACS will acually delete it when it runs...
>