Good evening,

I realized that the problem was related to the VMhost profile, so when I
checked I found that the VMhost profile user wasn’t set and I fixed it by
providing the correct user.

We are using Ubuntu 10.04 as the VM but the image capture didn’t went well
because the iamage capture try to copy the SSH daemon from /etc/ssh/sshd and
this path don’t exist under Ubuntu.

We switch the VM to Centos 5.5, and we tried the image captured again but it
failed because the image capture process can’t rename the VM in the VMware
repository.


We are absolutely in need of your assistance, please advise.


LOG:

2010-12-15 15:15:24|3867|vcld:main(166)|lastcheckin time updated for
management node 1: 2010-12-15 15:15:24

2010-12-15 15:15:31|14042|1:4|image|Module.pm:code_loop_timeout(413)|attempt
2: waiting for vmguest-2 to power off

2010-12-15 15:15:32|3867|vcld:main(166)|lastcheckin time updated for
management node 1: 2010-12-15 15:15:29

2010-12-15
15:15:36|14042|1:4|image|vSphere_SDK.pm:get_vm_power_state(359)|power state
of VM [standard] vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmx: on

2010-12-15 15:15:36|14042|1:4|image|Module.pm:code_loop_timeout(409)|attempt
2: code returned false, seconds elapsed/remaining: 21/579, sleeping for 15
seconds

2010-12-15 15:15:38|3867|vcld:main(166)|lastcheckin time updated for
management node 1: 2010-12-15 15:15:37

2010-12-15 15:15:44|3867|vcld:main(166)|lastcheckin time updated for
management node 1: 2010-12-15 15:15:43

2010-12-15 15:15:49|3867|vcld:main(166)|lastcheckin time updated for
management node 1: 2010-12-15 15:15:49

2010-12-15 15:15:51|14042|1:4|image|Module.pm:code_loop_timeout(413)|attempt
3: waiting for vmguest-2 to power off

2010-12-15
15:15:51|14042|1:4|image|vSphere_SDK.pm:get_vm_power_state(359)|power state
of VM [standard] vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmx: off

2010-12-15 15:15:51|14042|1:4|image|Module.pm:code_loop_timeout(416)|waiting
for vmguest-2 to power off, code returned true

2010-12-15
15:15:52|14042|1:4|image|vSphere_SDK.pm:get_file_info(1937)|searching for
matching file paths: base directory path: '[standard] vmwarelinux-base9-v2',
search pattern: 'vmwarelinux-base9-v2.vmdk'

2010-12-15 15:15:52|14042|1:4|image|vSphere_SDK.pm:find_files(1705)|matching
file count: 12

2010-12-15 15:15:52|14042|1:4|image|vSphere_SDK.pm:file_exists(1573)|file
exists: [standard] vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmdk

2010-12-15
15:15:52|14042|1:4|image|vSphere_SDK.pm:get_file_info(1937)|searching for
matching file paths: base directory path: '[standard] vmwarelinux-base9-v2',
search pattern: 'vmwarelinux-base9-v2.vmdk'

2010-12-15 15:15:53|14042|1:4|image|vSphere_SDK.pm:find_files(1705)|matching
file count: 12

2010-12-15 15:15:53|14042|1:4|image|vSphere_SDK.pm:file_exists(1573)|file
exists: [standard] vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmdk



|14042|1:4|image| ---- WARNING ----

|14042|1:4|image| 2010-12-15
15:15:53|14042|1:4|image|VMware.pm:rename_vmdk(3700)|destination vmdk file
path already exists: /var/lib/vmware/Virtual
Machines/vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmdk

|14042|1:4|image| ( 0) utils.pm, notify (line: 630)

|14042|1:4|image| (-1) VMware.pm, rename_vmdk (line: 3700)

|14042|1:4|image| (-2) VMware.pm, capture (line: 507)

|14042|1:4|image| (-3) image.pm, process (line: 165)

|14042|1:4|image| (-4) vcld, make_new_child (line: 595)

|14042|1:4|image| (-5) vcld, main (line: 342)





|14042|1:4|image| ---- WARNING ----

|14042|1:4|image| 2010-12-15
*15:15:53|14042|1:4|image|VMware.pm:capture(508)|failed
to rename the vmdk files after the VM was powered off:
'/var/lib/vmware/Virtual
Machines/vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmdk' -->
'/var/lib/vmware/Virtual
Machines/vmwarelinux-base9-v2/vmwarelinux-base9-v2.vmdk'*

*|14042|1:4|image| ( 0) utils.pm, notify (line: 630)*

*|14042|1:4|image| (-1) VMware.pm, capture (line: 508)*

*|14042|1:4|image| (-2) image.pm, process (line: 165)*

*|14042|1:4|image| (-3) vcld, make_new_child (line: 595)*

*|14042|1:4|image| (-4) vcld, main (line: 342)*

* *

* *

*|14042|1:4|image| ---- WARNING ---- *

*|14042|1:4|image| 2010-12-15
15:15:53|14042|1:4|image|image.pm:process(169)|vmwarelinux-base9-v2
image failed to be captured by provisioning module*

|14042|1:4|image| ( 0) utils.pm, notify (line: 630)

|14042|1:4|image| (-1) image.pm, process (line: 169)

|14042|1:4|image| (-2) vcld, make_new_child (line: 595)

|14042|1:4|image| (-3) vcld, main (line: 342)





|14042|1:4|image| ---- WARNING ----

|14042|1:4|image| 2010-12-15
15:15:53|14042|1:4|image|DataStructure.pm:_automethod(764)|corresponding
data has not been initialized for get_management_node_sysadmin_email:
$ENV{management_node_info}{SYSADMIN_EMAIL}

|14042|1:4|image| ( 0) utils.pm, notify (line: 630)

|14042|1:4|image| (-1) DataStructure.pm, _automethod (line: 764)

|14042|1:4|image| (-2) Autoload.pm, __ANON__ (line: 80)

|14042|1:4|image| (-3) image.pm, reservation_failed (line: 390)

|14042|1:4|image| (-4) image.pm, process (line: 170)

|14042|1:4|image| (-5) vcld, make_new_child (line: 595)

|14042|1:4|image| (-6) vcld, main (line: 342)

Reply via email to