[VCL-649] Images may fail to load if renamed in database by VMware code

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.3.1
• Component/s: database, vcld (backend)
• Assignee: Andrew Kurth
• Reporter: Andrew Kurth
• Created: 27/Nov/12 21:16
• Updated: 10/Dec/12 19:43
• Resolved: 10/Dec/12 19:43

Description

The VMware code will rename an image in the database when a vmdk is copied if the name is too long. This causes problems in environments that use multiple image repositories or datastores.

An image captured using VIM_SSH.pm under standalone ESXi will use the full image name. If the image is then copied by vSphere_SDK.pm, the name may be shortened in the database. The image will then fail to load on existing hosts which already have the image in their repository and/or datastore saved using the long name.

When a reservation starts, the shortened name is retrieved from the database. VIM_SSH.pm will then attempt to locate the image with the shortened name in the repository and/or datastore path but no image exists with that name.