GitHub user svenknockaert created a discussion: Failed to create template from
volume
We are experiencing an issue when creating a template from an instance’s volume.
In the GUI, the process seems to complete successfully — the status shows as
“ready.”
However, when this image is then used to deploy (and start) a new instance, an
error appears:
```
Error
Unable to start a VM [587b6b50-9b00-4604-b0e6-992e7013b110] due to [Unable to
create a deployment for VM instance
{"id":447,"instanceName":"i-71-447-VM","state":"Starting","type":"User","uuid":"587b6b50-9b00-4604-b0e6-992e7013b110"}].
```
The root cause of the problem is likely visible in the database:
Here is a working entry from te database:
```
+-------------+----+----------------------------------------------------------------+------------------------------------------------------------------------------------------------------+-----------------------------------------------------+------+
| template_id | id | install_path
| local_path
| error_str
| url |
+-------------+----+----------------------------------------------------------------+------------------------------------------------------------------------------------------------------+-----------------------------------------------------+------+
| 237 | 67 |
template/tmpl/2/237/916c05d8-fe0a-3290-a77b-0823c041db3d.qcow2 |
/mnt/SecStorage/1609b869-700e-3b63-876b-3c8abfd394d6/template/tmpl/2/237/dnld2323592655182356492tmp_
| Install completed successfully at 9/19/25, 10:30 AM | NULL |
+-------------+----+----------------------------------------------------------------+------------------------------------------------------------------------------------------------------+-----------------------------------------------------+------+
```
But with my last attempts i get:
```
+-------------+----+----------------------------------------------------------------+------------+-----------+------+
| template_id | id | install_path
| local_path | error_str | url |
+-------------+----+----------------------------------------------------------------+------------+-----------+------+
| 260 | 87 |
template/tmpl/2/260/b12973d6-5c82-4b6d-bfa4-e552b9ece7ff.qcow2 | NULL |
NULL | NULL |
+-------------+----+----------------------------------------------------------------+------------+-----------+------+
1 row in set (0.00 sec)
```
You can see that the “local_path” field is no longer populated, and there is
also no successful error_str entry.
However, the secondary storage is accessible to the CloudStack Management
Server, and the template has indeed been copied to the secondary storage (as
shown by the install_path).
What could be the reason why CloudStack no longer defines a local_path, causing
instance deployments based on that template to fail?
GitHub link: https://github.com/apache/cloudstack/discussions/11791
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
