[jira] [Resolved] (CLOUDSTACK-6159) [Hyper-v]Attached data volumes are getting created with disk name in primary storage

["Rajesh Battala (JIRA)" <ji...@apache.org>]

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

Rajesh Battala resolved CLOUDSTACK-6159.
----------------------------------------

    Resolution: Fixed

> [Hyper-v]Attached data volumes are getting created with disk name in primary storage
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6159
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6159
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller
>    Affects Versions: 4.3.0, 4.4.0
>            Reporter: Rajesh Battala
>            Assignee: Rajesh Battala
>              Labels: hyper-V,
>             Fix For: 4.3.0, 4.4.0
>
>
> [Hyper-v]Attached data volumes are getting created with disk name in primary storage
> Generally when we create a vm with root and data disks, they are stored in the primary storage with names ROOT-<instance-id>.vhd and DATA-<instance-id>.vhd respectively.
> But when we attach any disk to vm that is getting created with <diskname>.vhd format. Whereas in case of xenserver we created both root and data disks with uuid.vhd.
> Please follow the same approach for the sake of consistency.
> Steps to reproduce:
> ===================
> 1.Bring up CS in advanced zone with Hyper-v and use SMB/CIFS as the storage for both primary and secondary storage
> 2.Deploy one guest vm with default cent os template.
> 3.Create a volume (In UI>Storage->Add Volume) with small disk offering and name it as test.
> 4.Attach this volume to the instance created above
> Result:
> ========
> In primary storage root volume created with name ROOT-<instanceid> and data volume created with test.vhd



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