Hello, I'm trying to create a new revision of an image and it keeps failing when it tries to reload. I think part of the problem is that the master image file the it creates when it clones the source ends in 00001.vmdk and VCL is expected just <name of image > .vmdk. any idea what might be causing this? belong is a snippet of the log, please let me know if you need more. FYI, We recently upgraded to esxi 5.5 so I'm trying to upgrade the virtual hardware and VMware tools on the image.The golden image contains a file like the one listed below but VCL is expecting a different name..
vmwarewin7-SocialScience27-v5-000001.vmdk |31438|19:19|reload| ---- CRITICAL ---- |31438|19:19|reload| 2014-02-25 16:55:41|31438|19:19|reload|new.pm:reload_image(639)|vmwarewin7-SocialScience27-v5 does not exist on management node and could not be retrieved |31438|19:19|reload| ( 0) new.pm, reload_image (line: 639) |31438|19:19|reload| (-1) new.pm, process (line: 291) |31438|19:19|reload| (-2) vcld, make_new_child (line: 571) |31438|19:19|reload| (-3) vcld, main (line: 350) 2014-02-25 16:55:41|31438|19:19|reload|utils.pm:insertloadlog(3666)|inserted computer=4, failed, requested image does not exist on management node and could not be retrieved |31438|19:19|reload| ---- WARNING ---- |31438|19:19|reload| 2014-02-25 16:55:41|31438|19:19|reload|new.pm:process(339)|failed to load vcl-n-001 with vmwarewin7-SocialScience27-v5
