(cloudstack-documentation) branch main updated: Clarify consequences of deleting templates in use by VMs. (#355)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dahn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/main by this push:
     new 6010e07  Clarify consequences of deleting templates in use by VMs. (#355)
6010e07 is described below

commit 6010e075722c942b0ca429a52d50e5b9734e55b7
Author: Martin Emrich <ma...@martinemrich.me>
AuthorDate: Tue Oct 31 14:39:32 2023 +0100

    Clarify consequences of deleting templates in use by VMs. (#355)
---
 source/adminguide/templates.rst | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/source/adminguide/templates.rst b/source/adminguide/templates.rst
index 1e51658..ced7cf9 100644
--- a/source/adminguide/templates.rst
+++ b/source/adminguide/templates.rst
@@ -403,7 +403,8 @@ the Actions menu.
 Deleting Templates
 ------------------
 
-Templates may be deleted. In general, when a template spans multiple
+Templates may be deleted.  However when the templates are used the default 
+behaviour is to refuse deletion. In general, when a template spans multiple
 Zones, only the copy that is selected for deletion will be deleted; the
 same template in other Zones will not be deleted. The provided CentOS
 template is an exception to this. If the provided CentOS template is
@@ -413,6 +414,11 @@ When templates are deleted, the VMs instantiated from them will continue
 to run. However, new VMs cannot be created based on the deleted
 template.
 
+As said, Cloudstack refuses to delete a template when VMs based on the
+template exist. If this is the case, the parameter "forced" can be set 
+to "true" to delete the template anyways. These VMs can no longer be
+reinstalled from that template, but will be unaffected otherwise.
+
 Working with ISOs
 ===================