You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Devdeep Singh (JIRA)" <ji...@apache.org> on 2014/01/17 15:20:19 UTC

[jira] [Resolved] (CLOUDSTACK-5894) Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devdeep Singh resolved CLOUDSTACK-5894.
---------------------------------------

    Resolution: Fixed

> Create a Template from volume, restart management server. The template entry vanishes from cloud.template_store_ref table and template is no longer usable.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5894
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5894
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>            Priority: Critical
>              Labels: Hyper-V, hyper-V,, hyper-v
>             Fix For: 4.3.0
>
>
> Steps : 
>  =========================== 
> 1. Deploy an advanced zone setup of CS 4.3 with Hyper-V as the hypervisor type.
> 2. Create a VM. 
> 3. Stop the VM and create a Template from it's ROOT volume. 
> When the template is created, we can see in our secondary storage that the template.properties file gets created.
> 4. Now Deploy a VM from the template created in step 3 .  VM deployment goes fine. 
> 5. Now restart the management server. 
> After management server restart we find that the DB entry for that template in template_store_ref is gone.
> The template cannot be used for deploying an instance.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)