Parth Jagirdar created CLOUDSTACK-4545:
------------------------------------------
Summary: VMWare:Template:Cloning: Master templte used by linked
clones should not be available for deletion
Key: CLOUDSTACK-4545
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4545
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Template, VMware
Affects Versions: 4.2.1
Environment: VMWare
Reporter: Parth Jagirdar
Priority: Critical
Currently if we spawn Linked clone VM's; We can still delete the template used
by clones from cloudstack.
This master template is on primary storage and upon issuing delete it will be
cleaned eventually (from secondary and primary.
In this case We are likely to hit run-time exception and may affect all running
VM's (Linked Clones) if template is removed.
In Full clone scenario, we are less likely to encounter the exception and VM's
may not be affected at all.
In any case, We need a way such that when CM clones are actively using the
template we should mark that Master template as not available for deletion.
Same mechanism should be reflected on UI and templates used by VM's should
display delete button as grayed out with appropriate message like VM's are
actively using this template.
--
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: http://www.atlassian.com/software/jira
