I believe I got my datastore configured correctly now, but when I go
to capture an image I get the following in my log:
----------------------------------------------------------------------------
2011-02-24
15:29:00|7040|utils.pm:setup_get_array_choice(9986)|choices argument:
2011-02-24
15:29:00|7040|utils.pm:setup_get_array_choice(9986)|choices argument:
2011-02-24 15:29:08|7040|utils.pm:insert_request(8443)|inserted new
reload request into request table, request id=25
2011-02-24 15:29:08|7040|utils.pm:insert_request(8474)|inserted new
reload request into reservation table, reservation id=24
2011-02-24
15:29:11|2522|25:24|image|utils.pm:update_request_state(2049)|request
25 state updated to: pending, laststate to: image
2011-02-24
15:29:11|2522|25:24|image|utils.pm:insertloadlog(3933)|inserted
computer=2, begin, beginning to process, state is image
2011-02-24
15:29:11|7107|25:24|image|utils.pm:rename_vcld_process(7221)|renamed
process to 'vcld 25:24 image 192 vmwarewin7-testcap2826-v0 admin'
2011-02-24
15:29:11|7107|25:24|image|vSphere_SDK.pm:is_restricted(1079)|access
to the VM host via the vSphere SDK is NOT restricted due to the license
2011-02-24
15:29:18|7107|25:24|image|State.pm:initialize(128)|VCL::Module::Provisioning::VMware::VMware
provisioner object created
2011-02-24
15:29:18|7107|25:24|image|State.pm:initialize(151)|VCL::Module::OS::Windows::Version_6::7
OS object created
2011-02-24
15:29:18|7107|25:24|image|vcld:make_new_child(592)|VCL::image object
created and initialized
2011-02-24 15:29:18|7107|25:24|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: jabraze...@vcu.edu, VCL IMAGE Creation Started:
vmwarewin7-testcap2826-v0
2011-02-24 15:29:24|7107|25:24|image|image.pm:process(148)|image
vmwarewin7-testcap2826-v0 does not exist in the repository
2011-02-24 15:29:24|7107|25:24|image|image.pm:process(164)|calling
provisioning module's capture() subroutine
|7107|25:24|image| ---- WARNING ----
|7107|25:24|image| 2011-02-24
15:29:24|7107|25:24|image|VMware.pm:capture(403)|unable to capture
image, VM 192 is not responding to SSH
|7107|25:24|image| ( 0) utils.pm, notify (line: 630)
|7107|25:24|image| (-1) VMware.pm, capture (line: 403)
|7107|25:24|image| (-2) image.pm, process (line: 165)
|7107|25:24|image| (-3) vcld, make_new_child (line: 595)
|7107|25:24|image| (-4) vcld, main (line: 342)
|7107|25:24|image| ---- WARNING ----
|7107|25:24|image| 2011-02-24
15:29:24|7107|25:24|image|image.pm:process(169)|vmwarewin7-testcap2826-v0
image failed to be captured by provisioning module
|7107|25:24|image| ( 0) utils.pm, notify (line: 630)
|7107|25:24|image| (-1) image.pm, process (line: 169)
|7107|25:24|image| (-2) vcld, make_new_child (line: 595)
|7107|25:24|image| (-3) vcld, main (line: 342)
2011-02-24 15:29:24|7107|25:24|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: jabraze...@vcu.edu, PROBLEM -- image.pm
|7107|25:24|image| ---- CRITICAL ----
|7107|25:24|image| 2011-02-24
15:29:24|7107|25:24|image|image.pm:reservation_failed(393)|vmwarewin7-testcap2826-v0
image creation failed
|7107|25:24|image| ( 0) utils.pm, notify (line: 630)
|7107|25:24|image| (-1) image.pm, reservation_failed (line: 393)
|7107|25:24|image| (-2) image.pm, process (line: 170)
|7107|25:24|image| (-3) vcld, make_new_child (line: 595)
|7107|25:24|image| (-4) vcld, main (line: 342)
2011-02-24 15:29:24|7107|25:24|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: root@localhost, VCL -- NOTICE DELAY Image Creation
testcap28
2011-02-24 15:29:24|7107|25:24|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: jabraze...@vcu.edu, VCL -- NOTICE FAILED Image
Creation testcap28
2011-02-24
15:29:24|7107|25:24|image|utils.pm:update_request_state(2049)|request
25 state updated to: maintenance, laststate to: image
2011-02-24
15:29:24|7107|25:24|image|image.pm:reservation_failed(445)|request
state set to maintenance, laststate to image
2011-02-24
15:29:24|7107|25:24|image|utils.pm:update_computer_state(2091)|computer
2 state updated to: maintenance
2011-02-24
15:29:24|7107|25:24|image|image.pm:reservation_failed(453)|192 state
set to maintenance
2011-02-24
15:29:24|7107|25:24|image|image.pm:reservation_failed(460)|exiting
2011-02-24
15:29:24|7107|25:24|image|utils.pm:delete_computerloadlog_reservation(6876)|deleted
rows from computerloadlog for reservation id=24
2011-02-24 15:29:24|7107|25:24|image|State.pm:DESTROY(946)|VCL::image
process 7107 exiting
2011-02-24
15:29:00|7040|utils.pm:setup_get_array_choice(9986)|choices argument:
2011-02-24
15:29:00|7040|utils.pm:setup_get_array_choice(9986)|choices argument:
2011-02-24 15:29:08|7040|utils.pm:insert_request(8443)|inserted new
reload request into request table, request id=25
2011-02-24 15:29:08|7040|utils.pm:insert_request(8474)|inserted new
reload request into reservation table, reservation id=24
2011-02-24
15:29:11|2522|25:24|image|utils.pm:update_request_state(2049)|request
25 state updated to: pending, laststate to: image
2011-02-24
15:29:11|2522|25:24|image|utils.pm:insertloadlog(3933)|inserted
computer=2, begin, beginning to process, state is image
2011-02-24
15:29:11|7107|25:24|image|utils.pm:rename_vcld_process(7221)|renamed
process to 'vcld 25:24 image 192 vmwarewin7-testcap2826-v0 admin'
2011-02-24
15:29:11|7107|25:24|image|vSphere_SDK.pm:is_restricted(1079)|access
to the VM host via the vSphere SDK is NOT restricted due to the license
2011-02-24
15:29:18|7107|25:24|image|State.pm:initialize(128)|VCL::Module::Provisioning::VMware::VMware
provisioner object created
2011-02-24
15:29:18|7107|25:24|image|State.pm:initialize(151)|VCL::Module::OS::Windows::Version_6::7
OS object created
2011-02-24
15:29:18|7107|25:24|image|vcld:make_new_child(592)|VCL::image object
created and initialized
2011-02-24 15:29:18|7107|25:24|image|utils.pm:mail(1247)|SUCCESS --
Sending mail To: jabraze...@vcu.edu, VCL IMAGE Creation Started:
vmwarewin7-testcap2826-v0
2011-02-24 15:29:24|7107|25:24|image|image.pm:process(148)|image
vmwarewin7-testcap2826-v0 does not exist in the repository
2011-02-24 15:29:24|7107|25:24|image|image.pm:process(164)|calling
provisioning module's capture() subroutine
|7107|25:24|image| ---- WARNING ----
|7107|25:24|image| 2011-02-24
15:29:24|7107|25:24|image|VMware.pm:capture(403)|unable to capture
image, VM 192 is not responding to SSH
|7107|25:24|image| ( 0) utils.pm, notify (line: 630)
|7107|25:24|image| (-1) VMware.pm, capture (line: 403)
|7107|25:24|image| (-2) image.pm, process (line: 165)
|7107|25:24|image| (-3) vcld, make_new_child (line: 595)
I can ssh directly into the target VM from the management node. One
thing that does seem weird is that it refers to the VM as 196, as if
it forgot the last three octets of the VM name. Where should I look
to figure out what its missing?