cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9607) Preventing template deletion when template is in use.
Date Fri, 17 Feb 2017 17:40:42 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872181#comment-15872181
] 

ASF GitHub Bot commented on CLOUDSTACK-9607:
--------------------------------------------

Github user serg38 commented on the issue:

    https://github.com/apache/cloudstack/pull/1773
  
    @priyankparihar @ustcweizhou There seems to be just one case where it will affect resetVM
operations. If template is deleted and root disk is migrated to another PS where there is
no template copy at destination and the reset VM wont work. It is probably not easy to implement
copying a base template from on PS to another as a part of migrate volume command. I think
the right approach would be just to have a check in resetVM and if no local template copy
is available then find another PS with template copy and reset root disk over there or if
at that point there is no PS with template copy  gracefully error out resetVM command.


> Preventing template deletion when template is in use.
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-9607
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9607
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Priyank Parihar
>            Assignee: Priyank Parihar
>
> Consider this scenario:
> 1. User launches a VM from Template and keep it running
> 2. Admin logins and deleted that template [CloudPlatform does not check existing / running
VM etc. while the deletion is done]
> 3. User resets the VM
> 4. CloudPlatform fails to star the VM as it cannot find the corresponding template.
> It throws error as 
> java.lang.RuntimeException: Job failed due to exception Resource [Host:11] is unreachable:
Host 11: Unable to start instance due to can't find ready template: 209 for data center 1
>         at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:113)
>         at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:495)
> Client is requesting better handing of this scenario. We need to check existing / running
VM's when the template is deleted and warn admin about the possible issue that may occur.
> REPRO STEPS
> ==================
> 1. Launches a VM from Template and keep it running
> 2. Now delete that template 
> 3. Reset the VM
> 4. CloudPlatform fails to star the VM as it cannot find the corresponding template.
> EXPECTED BEHAVIOR
> ==================
> Cloud platform should throw some warning message while the template is deleted if that
template is being used by existing / running VM's
> ACTUAL BEHAVIOR
> ==================
> Cloud platform does not throw as waring etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message