cloudstack-dev 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-357) ISOs can be deleted while still attached to a running VM, and they subsequently cannot be detached from a running VM
Date Mon, 25 Feb 2013 10:34:12 GMT


ASF subversion and git services commented on CLOUDSTACK-357:

Commit 4d573ddd1bcd4ab27edfb91791a830308236521b in branch refs/heads/master from [~deeptid]
[;h=4d573dd ]

CLOUDSTACK-357 ISOs can be deleted while still attached to a running VM, and they subsequently
cannot be detached from a running VM

I made the changes to make sure that:
1. ISO will be deleted from the UI, but it is not deleted from the secondary storage as long
as it is attached to a VM.
2. The storage cleanup thread will check whether the iso is attached to any vm, if not, it
removes the ISO from the secondary storage.
3. Detach operation is now working which was failing before for the vms having attached iso(deleted).

Updated the patch for template sync during MS restart.

Manually tested the following:
setup: upload ISO1 and ISO 2
Attach ISO1 to VM1 and VM2
Attach ISO2 to VM3
set storage.cleanup.interval to 300

test cases:
1. delete ISO1 from UI, gets deleted
2. In VM Details of VM1 and VM2, can see detach ISO option
3. ISO1 exists in secondary storage
4. detach ISO1 from VM1, successful
5. ISO1 still exists in secondary storage.
6. Restart MS, template sync will not delete ISO1.
7. Detach ISO1 from VM2, successfull detached.
8. Wait for storage cleanup thread to execute, ISO1 gets deleted from Secondary storage.
9. Detach ISO2 from VM3
10.ISO2 exists in secondary storage, Delete ISO2 form UI, get deleted from secondary storage.

> ISOs can be deleted while still attached to a running VM, and they subsequently cannot
be detached from a running VM
> --------------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-357
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: ISO
>    Affects Versions: pre-4.0.0
>            Reporter: deepti dohare
>            Assignee: deepti dohare
>            Priority: Minor
>             Fix For: 4.1.0
> If an ISO is attached to a running VM, and you delete that ISO via CloudStack, the ISO
file is deleted from secondary storage. However, it is left attached to the running VM, and
it cannot be detached while the VM is running. The exception given in the log is pasted below
(full snippet attached). It appears that CloudStack is not even trying to detach it (no tasks
show up on vSphere). 
> Shutting down the VM and detaching the ISO works fine, but this is an inconvenience at
the least and should be handled better. For example, ISO deletion could fail if it is attached
to any VM, ISOs could be automatically detached from VMs before being deleted, or deleted
ISOs could be detachable from running VMs. 
> 2012-08-24 08:53:09,785 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-29:job-98)
Executing for job-98 
> 2012-08-24 08:53:09,801 WARN [] (Job-Executor-29:job-98)
Unable to find secondary storage in zone id=1 
> 2012-08-24 08:53:09,801 WARN [cloud.vm.UserVmManagerImpl] (Job-Executor-29:job-98) Couldn't
get absolute iso path 
> 2012-08-24 08:53:09,808 ERROR [cloud.api.ApiDispatcher] (Job-Executor-29:job-98) Exception
while executing DetachIsoCmd: 
> Failed to detach iso 
>         at

>         at

>         at 
>         at 
>         at$ 
>         at java.util.concurrent.Executors$ 
>         at java.util.concurrent.FutureTask$Sync.innerRun( 
>         at 
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(

>         at java.util.concurrent.ThreadPoolExecutor$

>         at 
> 2012-08-24 08:53:09,809 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-29:job-98)
Complete async job-98, jobStatus: 2, resultCode: 530, result:

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