[
https://issues.apache.org/jira/browse/CLOUDSTACK-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874755#comment-15874755
]
ASF GitHub Bot commented on CLOUDSTACK-9607:
--------------------------------------------
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@ustcweizhou @priyankparihar @borisstoyanov The default behavior was always
equivalent of force=true. We seem to agree that the UI behavior should remain
forced=true but with extra warning. We can either change default confirmation
"Please confirm that you want to delete this template." e.g. to "Please confirm
that you want to delete this template. Features that depends on the template
presence might no longer work". But I think the better option will be to have
response tag in listTemplate call to indicate if active VMs exists or not. Then
warning can be given only to such templates.
As for API side we might still change default behavior but we need to
explicitly document it in Release Notes so users can get prepared and change
instances of deleteTemplate execution to use forced=true or not as needed.
> 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)
