[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devdeep Singh resolved CLOUDSTACK-5462. --------------------------------------- Resolution: Fixed Reviewed and pushed the changes by Donal > Hyper-V Agent confused by existing volume of different image type > ----------------------------------------------------------------- > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > 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 > Reporter: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)