[
https://issues.apache.org/jira/browse/CLOUDSTACK-9720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786963#comment-15786963
]
ASF GitHub Bot commented on CLOUDSTACK-9720:
--------------------------------------------
Github user sureshanaparti commented on the issue:
https://github.com/apache/cloudstack/pull/1880
Validated that the template_size is getting updated correctly in
template_spool_ref table.
Prior to the fix, the size was logged as 0 =>
mysql> select id,template_id,template_size from template_spool_ref;
---------------------------------
id template_id template_size
---------------------------------
1 8 0
2 202 0
3 7 0
7 8 0
10 8 0
15 8 0
23 202 0
25 202 0
---------------------------------
After the fix correct size is getting updated=>
mysql> select id,template_id,template_size from template_spool_ref;
---------------------------------
id template_id template_size
---------------------------------
1 8 2621440000
2 202 3145728000
3 7 2147483648
---------------------------------
3 rows in set (0.00 sec)
> [VMware] template_spool_ref table is not getting updated with correct
> template physical size in template_size column.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9720
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9720
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
> Reporter: Suresh Kumar Anaparti
> Assignee: Suresh Kumar Anaparti
> Fix For: 4.10.0.0
>
>
> CloudStack is not updating template_spool_ref table with correct template
> physical_size in template_size column which leads to incorrect calculation of
> allocated primary storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
