You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@vcl.apache.org by David DeMizio <dd...@ncf.edu> on 2014/02/25 23:03:09 UTC
can't capture image revision
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
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
well, I was able to ssh into esxi host and run vmkfstools -E
vmwarewin7-olab18-v2-000001.vmdk vmwarewin7-olab18
-v2.vmdk and that seems to allow the new revision to load. this has been
happening since 5.5 upgrade because I was attempting to update the VMware
hardware and VMware tools on the images.
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Wed, Feb 26, 2014 at 11:11 AM, David DeMizio <dd...@ncf.edu> wrote:
> Same issue with another image that had a very short name . When I ssh to
> to esxi host the files below exist
>
> -rw------- 1 root root 107374182400 Feb 26 2014
> vmwarewin7-olab18-v2-000001-flat.vmdk
> -rw------- 1 root root 565 Feb 26 2014
> vmwarewin7-olab18-v2-000001.vmdk
> -rw------- 1 root root 3230 Feb 26 11:06
> vmwarewin7-olab18-v2.vmx.reference
>
> David DeMizio
> *Academic Systems Coordinator*
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Wed, Feb 26, 2014 at 10:38 AM, David DeMizio <dd...@ncf.edu> wrote:
>
>> Sorry, forgot to mention that it's a different name from my previous post
>> because I shortened the name when I chose create image instead of create
>> revision
>>
>> David DeMizio
>> *Academic Systems Coordinator*
>> Office of Information Technology
>> New College of Florida
>> Phone: 941-487-4222 | Fax: 941-487-4356
>> www.ncf.edu
>>
>>
>> On Wed, Feb 26, 2014 at 10:35 AM, David DeMizio <dd...@ncf.edu> wrote:
>>
>>> The folder structure is
>>> vmwarewin7-SSRLVCL28-v0\vmwarewin7-SSRLVCL28-v0-000001.vmdk which is about
>>> 44GB in size so it's the virtual disk extent. In the same folder there is
>>> the vmwarewin7-SSRLVCL28-v0.vmx.reference
>>>
>>> David DeMizio
>>> *Academic Systems Coordinator*
>>> Office of Information Technology
>>> New College of Florida
>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>> www.ncf.edu
>>>
>>>
>>> On Wed, Feb 26, 2014 at 10:24 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>
>>>>
>>>> On Feb 26, 2014, at 10:02 AM, David DeMizio <dd...@ncf.edu> wrote:
>>>>
>>>> Ok..I'll try a complete fresh capture of base image, I tried to create
>>>> image via vcl frontend and when It asked me if I wanted to create a new
>>>> image or create a revision, I chose new image and same issue.
>>>>
>>>>
>>>> Just to clarify, is the virtual disk located in a directory like so?
>>>>
>>>>
>>>> vmwarewin7-SocialScience27-v5-000001/vmwarewin7-SocialScience27-v5-000001.vmdk
>>>>
>>>> And is that the location of the vmdk metadata file or the virtual disk
>>>> extent?
>>>>
>>>>
>>>>
>>>> I'll try it from vcld. Do you think I need to update the Perl SDK to
>>>> version 5.5 on VCL?
>>>>
>>>> David DeMizio
>>>> *Academic Systems Coordinator*
>>>> Office of Information Technology
>>>> New College of Florida
>>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>>> www.ncf.edu
>>>>
>>>>
>>>> On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>>
>>>>> I'm referring to both capturing a base image through vcld and creating
>>>>> a new image based off of an existing environment. I am not referring to
>>>>> creating a new revision of an existing image.
>>>>>
>>>>> Aaron
>>>>>
>>>>>
>>>>> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>>>>>
>>>>> Thanks Aaron,
>>>>>
>>>>> So from the VCL front end before going to manage ->create update
>>>>> images , I need to rename it in the edit details from the edit image
>>>>> profiles menu or are you referring to capturing an image from scratch(base
>>>>> image) and not a revision?
>>>>>
>>>>> David DeMizio
>>>>> *Academic Systems Coordinator*
>>>>> Office of Information Technology
>>>>> New College of Florida
>>>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>>>> www.ncf.edu
>>>>>
>>>>>
>>>>> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>>>
>>>>>> I don't use vmware 5.5, but on earlier versions that use vCenter,
>>>>>> there is an issue where, if a virtual machine name is longer than 29
>>>>>> characters, vmware will silently truncate the name and append an
>>>>>> incrementable (numerical) value. To a user of vCenter the name appears
>>>>>> correct, though in the underlying datastore, it is actually different (even
>>>>>> though the vmware documentation explain that any VM can have names up to 80
>>>>>> characters in length).
>>>>>>
>>>>>> I thought there was code in place to handle this, but I could be
>>>>>> mistaken. In any case, the simple way around it is to give your image a
>>>>>> shorter name when you initiate the capture. Then, once the image capture is
>>>>>> complete, you can rename it to anything you'd like through the VCL web
>>>>>> front-end.
>>>>>>
>>>>>> -Aaron
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>>>>>
>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
Same issue with another image that had a very short name . When I ssh to to
esxi host the files below exist
-rw------- 1 root root 107374182400 Feb 26 2014
vmwarewin7-olab18-v2-000001-flat.vmdk
-rw------- 1 root root 565 Feb 26 2014
vmwarewin7-olab18-v2-000001.vmdk
-rw------- 1 root root 3230 Feb 26 11:06
vmwarewin7-olab18-v2.vmx.reference
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Wed, Feb 26, 2014 at 10:38 AM, David DeMizio <dd...@ncf.edu> wrote:
> Sorry, forgot to mention that it's a different name from my previous post
> because I shortened the name when I chose create image instead of create
> revision
>
> David DeMizio
> *Academic Systems Coordinator*
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Wed, Feb 26, 2014 at 10:35 AM, David DeMizio <dd...@ncf.edu> wrote:
>
>> The folder structure is
>> vmwarewin7-SSRLVCL28-v0\vmwarewin7-SSRLVCL28-v0-000001.vmdk which is about
>> 44GB in size so it's the virtual disk extent. In the same folder there is
>> the vmwarewin7-SSRLVCL28-v0.vmx.reference
>>
>> David DeMizio
>> *Academic Systems Coordinator*
>> Office of Information Technology
>> New College of Florida
>> Phone: 941-487-4222 | Fax: 941-487-4356
>> www.ncf.edu
>>
>>
>> On Wed, Feb 26, 2014 at 10:24 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>>
>>>
>>> On Feb 26, 2014, at 10:02 AM, David DeMizio <dd...@ncf.edu> wrote:
>>>
>>> Ok..I'll try a complete fresh capture of base image, I tried to create
>>> image via vcl frontend and when It asked me if I wanted to create a new
>>> image or create a revision, I chose new image and same issue.
>>>
>>>
>>> Just to clarify, is the virtual disk located in a directory like so?
>>>
>>>
>>> vmwarewin7-SocialScience27-v5-000001/vmwarewin7-SocialScience27-v5-000001.vmdk
>>>
>>> And is that the location of the vmdk metadata file or the virtual disk
>>> extent?
>>>
>>>
>>>
>>> I'll try it from vcld. Do you think I need to update the Perl SDK to
>>> version 5.5 on VCL?
>>>
>>> David DeMizio
>>> *Academic Systems Coordinator*
>>> Office of Information Technology
>>> New College of Florida
>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>> www.ncf.edu
>>>
>>>
>>> On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>
>>>> I'm referring to both capturing a base image through vcld and creating
>>>> a new image based off of an existing environment. I am not referring to
>>>> creating a new revision of an existing image.
>>>>
>>>> Aaron
>>>>
>>>>
>>>> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>>>>
>>>> Thanks Aaron,
>>>>
>>>> So from the VCL front end before going to manage ->create update
>>>> images , I need to rename it in the edit details from the edit image
>>>> profiles menu or are you referring to capturing an image from scratch(base
>>>> image) and not a revision?
>>>>
>>>> David DeMizio
>>>> *Academic Systems Coordinator*
>>>> Office of Information Technology
>>>> New College of Florida
>>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>>> www.ncf.edu
>>>>
>>>>
>>>> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>>
>>>>> I don't use vmware 5.5, but on earlier versions that use vCenter,
>>>>> there is an issue where, if a virtual machine name is longer than 29
>>>>> characters, vmware will silently truncate the name and append an
>>>>> incrementable (numerical) value. To a user of vCenter the name appears
>>>>> correct, though in the underlying datastore, it is actually different (even
>>>>> though the vmware documentation explain that any VM can have names up to 80
>>>>> characters in length).
>>>>>
>>>>> I thought there was code in place to handle this, but I could be
>>>>> mistaken. In any case, the simple way around it is to give your image a
>>>>> shorter name when you initiate the capture. Then, once the image capture is
>>>>> complete, you can rename it to anything you'd like through the VCL web
>>>>> front-end.
>>>>>
>>>>> -Aaron
>>>>>
>>>>>
>>>>>
>>>>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
Sorry, forgot to mention that it's a different name from my previous post
because I shortened the name when I chose create image instead of create
revision
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Wed, Feb 26, 2014 at 10:35 AM, David DeMizio <dd...@ncf.edu> wrote:
> The folder structure is
> vmwarewin7-SSRLVCL28-v0\vmwarewin7-SSRLVCL28-v0-000001.vmdk which is about
> 44GB in size so it's the virtual disk extent. In the same folder there is
> the vmwarewin7-SSRLVCL28-v0.vmx.reference
>
> David DeMizio
> *Academic Systems Coordinator*
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Wed, Feb 26, 2014 at 10:24 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>
>>
>> On Feb 26, 2014, at 10:02 AM, David DeMizio <dd...@ncf.edu> wrote:
>>
>> Ok..I'll try a complete fresh capture of base image, I tried to create
>> image via vcl frontend and when It asked me if I wanted to create a new
>> image or create a revision, I chose new image and same issue.
>>
>>
>> Just to clarify, is the virtual disk located in a directory like so?
>>
>>
>> vmwarewin7-SocialScience27-v5-000001/vmwarewin7-SocialScience27-v5-000001.vmdk
>>
>> And is that the location of the vmdk metadata file or the virtual disk
>> extent?
>>
>>
>>
>> I'll try it from vcld. Do you think I need to update the Perl SDK to
>> version 5.5 on VCL?
>>
>> David DeMizio
>> *Academic Systems Coordinator*
>> Office of Information Technology
>> New College of Florida
>> Phone: 941-487-4222 | Fax: 941-487-4356
>> www.ncf.edu
>>
>>
>> On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu>wrote:
>>
>>> I'm referring to both capturing a base image through vcld and creating a
>>> new image based off of an existing environment. I am not referring to
>>> creating a new revision of an existing image.
>>>
>>> Aaron
>>>
>>>
>>> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>>>
>>> Thanks Aaron,
>>>
>>> So from the VCL front end before going to manage ->create update images
>>> , I need to rename it in the edit details from the edit image profiles
>>> menu or are you referring to capturing an image from scratch(base image)
>>> and not a revision?
>>>
>>> David DeMizio
>>> *Academic Systems Coordinator*
>>> Office of Information Technology
>>> New College of Florida
>>> Phone: 941-487-4222 | Fax: 941-487-4356
>>> www.ncf.edu
>>>
>>>
>>> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu>wrote:
>>>
>>>> I don't use vmware 5.5, but on earlier versions that use vCenter, there
>>>> is an issue where, if a virtual machine name is longer than 29 characters,
>>>> vmware will silently truncate the name and append an incrementable
>>>> (numerical) value. To a user of vCenter the name appears correct, though in
>>>> the underlying datastore, it is actually different (even though the vmware
>>>> documentation explain that any VM can have names up to 80 characters in
>>>> length).
>>>>
>>>> I thought there was code in place to handle this, but I could be
>>>> mistaken. In any case, the simple way around it is to give your image a
>>>> shorter name when you initiate the capture. Then, once the image capture is
>>>> complete, you can rename it to anything you'd like through the VCL web
>>>> front-end.
>>>>
>>>> -Aaron
>>>>
>>>>
>>>>
>>>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>>>
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
The folder structure is
vmwarewin7-SSRLVCL28-v0\vmwarewin7-SSRLVCL28-v0-000001.vmdk which is about
44GB in size so it's the virtual disk extent. In the same folder there is
the vmwarewin7-SSRLVCL28-v0.vmx.reference
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Wed, Feb 26, 2014 at 10:24 AM, Aaron Coburn <ac...@amherst.edu> wrote:
>
> On Feb 26, 2014, at 10:02 AM, David DeMizio <dd...@ncf.edu> wrote:
>
> Ok..I'll try a complete fresh capture of base image, I tried to create
> image via vcl frontend and when It asked me if I wanted to create a new
> image or create a revision, I chose new image and same issue.
>
>
> Just to clarify, is the virtual disk located in a directory like so?
>
>
> vmwarewin7-SocialScience27-v5-000001/vmwarewin7-SocialScience27-v5-000001.vmdk
>
> And is that the location of the vmdk metadata file or the virtual disk
> extent?
>
>
>
> I'll try it from vcld. Do you think I need to update the Perl SDK to
> version 5.5 on VCL?
>
> David DeMizio
> *Academic Systems Coordinator*
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu> wrote:
>
>> I'm referring to both capturing a base image through vcld and creating a
>> new image based off of an existing environment. I am not referring to
>> creating a new revision of an existing image.
>>
>> Aaron
>>
>>
>> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>>
>> Thanks Aaron,
>>
>> So from the VCL front end before going to manage ->create update images
>> , I need to rename it in the edit details from the edit image profiles
>> menu or are you referring to capturing an image from scratch(base image)
>> and not a revision?
>>
>> David DeMizio
>> *Academic Systems Coordinator*
>> Office of Information Technology
>> New College of Florida
>> Phone: 941-487-4222 | Fax: 941-487-4356
>> www.ncf.edu
>>
>>
>> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu>wrote:
>>
>>> I don't use vmware 5.5, but on earlier versions that use vCenter, there
>>> is an issue where, if a virtual machine name is longer than 29 characters,
>>> vmware will silently truncate the name and append an incrementable
>>> (numerical) value. To a user of vCenter the name appears correct, though in
>>> the underlying datastore, it is actually different (even though the vmware
>>> documentation explain that any VM can have names up to 80 characters in
>>> length).
>>>
>>> I thought there was code in place to handle this, but I could be
>>> mistaken. In any case, the simple way around it is to give your image a
>>> shorter name when you initiate the capture. Then, once the image capture is
>>> complete, you can rename it to anything you'd like through the VCL web
>>> front-end.
>>>
>>> -Aaron
>>>
>>>
>>>
>>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Re: can't capture image revision
Posted by Aaron Coburn <ac...@amherst.edu>.
On Feb 26, 2014, at 10:02 AM, David DeMizio <dd...@ncf.edu> wrote:
> Ok..I'll try a complete fresh capture of base image, I tried to create image via vcl frontend and when It asked me if I wanted to create a new image or create a revision, I chose new image and same issue.
Just to clarify, is the virtual disk located in a directory like so?
vmwarewin7-SocialScience27-v5-000001/vmwarewin7-SocialScience27-v5-000001.vmdk
And is that the location of the vmdk metadata file or the virtual disk extent?
> I'll try it from vcld. Do you think I need to update the Perl SDK to version 5.5 on VCL?
>
> David DeMizio
> Academic Systems Coordinator
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu> wrote:
> I’m referring to both capturing a base image through vcld and creating a new image based off of an existing environment. I am not referring to creating a new revision of an existing image.
>
> Aaron
>
>
> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>
>> Thanks Aaron,
>>
>> So from the VCL front end before going to manage ->create update images , I need to rename it in the edit details from the edit image profiles menu or are you referring to capturing an image from scratch(base image) and not a revision?
>>
>> David DeMizio
>> Academic Systems Coordinator
>> Office of Information Technology
>> New College of Florida
>> Phone: 941-487-4222 | Fax: 941-487-4356
>> www.ncf.edu
>>
>>
>> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu> wrote:
>> I don’t use vmware 5.5, but on earlier versions that use vCenter, there is an issue where, if a virtual machine name is longer than 29 characters, vmware will silently truncate the name and append an incrementable (numerical) value. To a user of vCenter the name appears correct, though in the underlying datastore, it is actually different (even though the vmware documentation explain that any VM can have names up to 80 characters in length).
>>
>> I thought there was code in place to handle this, but I could be mistaken. In any case, the simple way around it is to give your image a shorter name when you initiate the capture. Then, once the image capture is complete, you can rename it to anything you’d like through the VCL web front-end.
>>
>> -Aaron
>>
>>
>>
>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>
>>> 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
>>>
>>>
>>>
>>>
>>
>>
>
>
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
Ok..I'll try a complete fresh capture of base image, I tried to create
image via vcl frontend and when It asked me if I wanted to create a new
image or create a revision, I chose new image and same issue. I'll try it
from vcld. Do you think I need to update the Perl SDK to version 5.5 on VCL?
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Wed, Feb 26, 2014 at 9:51 AM, Aaron Coburn <ac...@amherst.edu> wrote:
> I'm referring to both capturing a base image through vcld and creating a
> new image based off of an existing environment. I am not referring to
> creating a new revision of an existing image.
>
> Aaron
>
>
> On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
>
> Thanks Aaron,
>
> So from the VCL front end before going to manage ->create update images ,
> I need to rename it in the edit details from the edit image profiles menu
> or are you referring to capturing an image from scratch(base image) and not
> a revision?
>
> David DeMizio
> *Academic Systems Coordinator*
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu> wrote:
>
>> I don't use vmware 5.5, but on earlier versions that use vCenter, there
>> is an issue where, if a virtual machine name is longer than 29 characters,
>> vmware will silently truncate the name and append an incrementable
>> (numerical) value. To a user of vCenter the name appears correct, though in
>> the underlying datastore, it is actually different (even though the vmware
>> documentation explain that any VM can have names up to 80 characters in
>> length).
>>
>> I thought there was code in place to handle this, but I could be
>> mistaken. In any case, the simple way around it is to give your image a
>> shorter name when you initiate the capture. Then, once the image capture is
>> complete, you can rename it to anything you'd like through the VCL web
>> front-end.
>>
>> -Aaron
>>
>>
>>
>> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>>
>> 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
>>
>>
>>
>>
>>
>>
>
>
Re: can't capture image revision
Posted by Aaron Coburn <ac...@amherst.edu>.
I’m referring to both capturing a base image through vcld and creating a new image based off of an existing environment. I am not referring to creating a new revision of an existing image.
Aaron
On Feb 26, 2014, at 8:55 AM, David DeMizio <dd...@ncf.edu> wrote:
> Thanks Aaron,
>
> So from the VCL front end before going to manage ->create update images , I need to rename it in the edit details from the edit image profiles menu or are you referring to capturing an image from scratch(base image) and not a revision?
>
> David DeMizio
> Academic Systems Coordinator
> Office of Information Technology
> New College of Florida
> Phone: 941-487-4222 | Fax: 941-487-4356
> www.ncf.edu
>
>
> On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu> wrote:
> I don’t use vmware 5.5, but on earlier versions that use vCenter, there is an issue where, if a virtual machine name is longer than 29 characters, vmware will silently truncate the name and append an incrementable (numerical) value. To a user of vCenter the name appears correct, though in the underlying datastore, it is actually different (even though the vmware documentation explain that any VM can have names up to 80 characters in length).
>
> I thought there was code in place to handle this, but I could be mistaken. In any case, the simple way around it is to give your image a shorter name when you initiate the capture. Then, once the image capture is complete, you can rename it to anything you’d like through the VCL web front-end.
>
> -Aaron
>
>
>
> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>
>> 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
>>
>>
>>
>>
>
>
Re: can't capture image revision
Posted by David DeMizio <dd...@ncf.edu>.
Thanks Aaron,
So from the VCL front end before going to manage ->create update images , I
need to rename it in the edit details from the edit image profiles menu or
are you referring to capturing an image from scratch(base image) and not a
revision?
David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu
On Tue, Feb 25, 2014 at 9:09 PM, Aaron Coburn <ac...@amherst.edu> wrote:
> I don't use vmware 5.5, but on earlier versions that use vCenter, there is
> an issue where, if a virtual machine name is longer than 29 characters,
> vmware will silently truncate the name and append an incrementable
> (numerical) value. To a user of vCenter the name appears correct, though in
> the underlying datastore, it is actually different (even though the vmware
> documentation explain that any VM can have names up to 80 characters in
> length).
>
> I thought there was code in place to handle this, but I could be mistaken.
> In any case, the simple way around it is to give your image a shorter name
> when you initiate the capture. Then, once the image capture is complete,
> you can rename it to anything you'd like through the VCL web front-end.
>
> -Aaron
>
>
>
> On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
>
> 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
>
>
>
>
>
>
Re: can't capture image revision
Posted by Aaron Coburn <ac...@amherst.edu>.
I don’t use vmware 5.5, but on earlier versions that use vCenter, there is an issue where, if a virtual machine name is longer than 29 characters, vmware will silently truncate the name and append an incrementable (numerical) value. To a user of vCenter the name appears correct, though in the underlying datastore, it is actually different (even though the vmware documentation explain that any VM can have names up to 80 characters in length).
I thought there was code in place to handle this, but I could be mistaken. In any case, the simple way around it is to give your image a shorter name when you initiate the capture. Then, once the image capture is complete, you can rename it to anything you’d like through the VCL web front-end.
-Aaron
On Feb 25, 2014, at 5:03 PM, David DeMizio <dd...@ncf.edu> wrote:
> 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
>
>
>
>