[ https://issues.apache.org/jira/browse/CLOUDSTACK-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874201#comment-15874201 ]
ASF GitHub Bot commented on CLOUDSTACK-9607: -------------------------------------------- Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1773 I agree with @serg38 and @ustcweizhou that upon deletion user should be displayed with an yes/no dialogue if there are deployed VMs, but a lot of CS user aren't using UI, but just the APIs. If the force option is enabled by default I guess the API call will go and delete the all selected templates without any warning. I think the `force=true` should only stay with the UI call. > 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)