[jira] [Assigned] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times

["Rohit Yadav (JIRA)" <ji...@apache.org>]

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

Rohit Yadav reassigned CLOUDSTACK-9528:
---------------------------------------

    Assignee: Rohit Yadav  (was: Abhinandan Prateek)

> SSVM Downloads (built-in) template multiple times
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-9528
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Secondary Storage, XenServer
>    Affects Versions: 4.8.1, 4.9.0
>         Environment: ACS 4.9 with XenServer 6.5SP1
> ACS 4.9 with VMware 5.5u3
>            Reporter: Paul Angus
>            Assignee: Rohit Yadav
>            Priority: Critical
>              Labels: 4.8.2.0-smoke-test-failure
>             Fix For: 4.9.1.0, 4.8.2.0, 4.10.1.0
>
>         Attachments: Capture.PNG, Capture2 (1).PNG, cloud_out
>
>
> SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in template multiple times (concurrently).
> Once this has happened the built-in template could not be used to deploy VMs as couldstack found 2 VHDs in the directory and threw an insufficient capacity exception.
> The template was being downloaded locally (at 35MB/s) with no drop outs.
> There are in fact multiple issues here:
> 1. SSVM not behaving properly and downloading mulitple copies.
> 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. The full path and filename of the VHD is in its data base, it should use it.
> 3. what is template.properties for? the filename is contained within it, as is an MDSUM to check for consistency
> 4. the filename in template.properties is different to the one in the database.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)