MartinEmrich commented on issue #8157:
URL: https://github.com/apache/cloudstack/issues/8157#issuecomment-1785033664
No stacktraces in the logs.
````
2023-10-30 12:51:32,525 DEBUG [c.c.a.ApiServlet]
(qtp1444635922-101117:ctx-7a8983e0) (logid:8661feb8) ===START=== 10.14.32.11
-- GET
id=f0bafad8-736a-4d15-905f-8afe957fa6a4&forced=false&zoneid=e99e796c-4e5c-4549-a0d7-ddd3d8526c06&command=deleteTemplate&response=json
````
This is the error message:
````
2023-10-30 12:51:32,575 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-36:ctx-aa4d8787 job-97867) (logid:f3b3e108) Complete async
job-97867, jobStatus: FAILED, resultCode: 431, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"431","errortext":"Unable
to delete template with id: 322 because VM instances: [VM instance
{"id":XXXX,"instanceName":"YYYYY","type":"User","uuid":"f8a0c75b-784d-4490-8e29-7fd9f179a4ca"}
(and lots more) ] are using it."}
````
I do not understand how running VMs are _using_ templates. On XenServer, the
ROOT volume ist copied from the template image; afterwards, I see no connection
between the running VM and the template.
Maybe there are other hypervisors with such a relation (e.g. running VMs in
a copy-on-write fashion laid over the active template image), but with Xen/XCP
that's not the case (and would be veeeery slow from NFS secondary storage if it
was the case).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
