You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2012/11/27 22:16:58 UTC
[jira] [Created] (VCL-649) Images may fail to load if renamed in
database by VMware code
Andy Kurth created VCL-649:
------------------------------
Summary: Images may fail to load if renamed in database by VMware code
Key: VCL-649
URL: https://issues.apache.org/jira/browse/VCL-649
Project: VCL
Issue Type: Bug
Components: database, vcld (backend)
Affects Versions: 2.3
Reporter: Andy Kurth
Assignee: Andy Kurth
Fix For: 2.3.1
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira