We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template details are lost when the template is deleted from one zone
Cloudstack version 4.19,4.20
Have a Cloudstack environment with 2 zones
Register a template in Zone 1 and a setting to the template for example UEFI=secure
mysql> select * from vm_template_details where template_id=208; +----+-------------+------+--------+---------+ | id | template_id | name | value | display | +----+-------------+------+--------+---------+ | 4 | 208 | UEFI | SECURE | 1 | +----+-------------+------+--------+---------+ 1 row in set (0.00 sec)
Copy the template to Zone 2.
Delete the template in zone2
Check the Template setting in zone 1
mysql> select * from vm_template_details where template_id=208; Empty set (0.00 sec)
Actual Behaviour
Currently cloudstack deletes the template settings if its deleted in one zone
Expected Behaviour
Cloudstack should not delete the template settings if its deleted in one zone
The text was updated successfully, but these errors were encountered:
No branches or pull requests
problem
Template details are lost when the template is deleted from one zone
versions
Cloudstack version 4.19,4.20
The steps to reproduce the bug
Have a Cloudstack environment with 2 zones
Register a template in Zone 1 and a setting to the template for example UEFI=secure
Copy the template to Zone 2.
Delete the template in zone2
Check the Template setting in zone 1
What to do about it?
Actual Behaviour
Currently cloudstack deletes the template settings if its deleted in one zone
Expected Behaviour
Cloudstack should not delete the template settings if its deleted in one zone
The text was updated successfully, but these errors were encountered: