[CLOUDSTACK-5462] Hyper-V Agent confused by existing volume of different image type

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.0
• Component/s: Hypervisor Controller
• Security Level: Public (Anyone can view this level - this is the default.)
• Labels: hyper-v
• Assignee: Donal Lafferty
• Reporter: Donal Lafferty
• Created: 11/Dec/13 14:32
• Updated: 13/Dec/13 02:40
• Resolved: 12/Dec/13 09:29

Description

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.