cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinav Roy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5795) [Hyper-V] When a Template is created from volume the db.properties file is not created, due to which when we restart management server, The DB entry for that Template is deleted from template_store_ref table and template becomes inaccessible
Date Mon, 06 Jan 2014 11:12:50 GMT

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

Abhinav Roy updated CLOUDSTACK-5795:
------------------------------------

    Attachment: CS-5795.jpg
                CS-5795.zip

> [Hyper-V] When a Template is created from volume the db.properties file is not created,
 due to which when we restart management server, The DB entry for that Template is deleted
from template_store_ref table and template becomes inaccessible
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5795
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5795
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, Management Server
>    Affects Versions: 4.3.0
>         Environment: Hyperv , 4.3
>            Reporter: Abhinav Roy
>            Priority: Critical
>              Labels: hyper-V,, hyper-v, hyperv
>             Fix For: 4.3.0
>
>         Attachments: CS-5795.jpg, CS-5795.zip
>
>
> 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.
> But when the template is created, we can see in our secondary storage that the template.properties
file doesn't get 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.
> Attaching management server logs , snapshot and DB dump.



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

Mime
View raw message