[
https://issues.apache.org/jira/browse/CLOUDSTACK-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256616#comment-14256616
]
Likitha Shetty commented on CLOUDSTACK-8109:
--------------------------------------------
When we create a private template, in case of VMware, it is expected to not
package the VMDKs into an OVA. Instead we simply keep the .ova.meta file in the
secondary storage which is a property file that has the relevant details about
the OVA. When a download command is issued for the private template, since the
OVA is not present, SSVM will package the OVA and then provide the URL pointing
to the OVA.
The bug in the OVA packaging was that, even though the OVA was successfully
packaged, the check for the OVA's existence returned false and resulted in the
failure of template extraction.
> [VMware] Extract Template is failing.
> --------------------------------------
>
> Key: CLOUDSTACK-8109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8109
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: Future
>
>
> +Steps to reproduce+
> 1. Deploy a VM.
> 2. Stop the VM.
> 3. Create template from VM’s root disk.
> 4. Try to download the template - FAILURE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
