[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786190#comment-15786190
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9720:
--------------------------------------------

GitHub user sureshanaparti opened a pull request:

    https://github.com/apache/cloudstack/pull/1880

    CLOUDSTACK-9720: [VMware] template_spool_ref table is not getting updated 
with correct template physical size in template_size column.

    Updated the template_spool_ref table with the correct template (VMware - 
OVA file) size.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9720

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1880.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1880
    
----
commit 84995b6ffbae565606ef050c0569815e7a87a8e1
Author: Suresh Kumar Anaparti <suresh.anapa...@accelerite.com>
Date:   2016-12-29T21:31:12Z

    CLOUDSTACK-9720: [VMware] template_spool_ref table is not getting updated 
with correct template physical size in template_size column.

----


> [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
>             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)

Reply via email to