I believe the updated code should fix your issue. I noticed the same thing after upgrading to 5.5. You will need to update both vSphere_SDK.pm and VMware.pm. Get them from "trunk" in the svn repository:
https://svn.apache.org/repos/asf/vcl/trunk/managementnode/lib/VCL/Module/Provisioning/VMware/VMware.pm https://svn.apache.org/repos/asf/vcl/trunk/managementnode/lib/VCL/Module/Provisioning/VMware/vSphere_SDK.pm -Andy On Fri, Aug 8, 2014 at 4:31 PM, David DeMizio <[email protected]> wrote: > Is this the fix to my issue, cause it started since I updated to 5.5 > > > https://svn.apache.org/viewvc/vcl/trunk/managementnode/lib/VCL/Module/Provisioning/VMware/vSphere_SDK.pm?view=log > > > 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 Fri, Aug 1, 2014 at 8:34 AM, David DeMizio <[email protected]> wrote: > >> Actually now that I remember, vcl created the image with <image >> name>-000001.vmdk and as I recall from previous post I had to manually log >> into the esxi and rename to just <image name>.vmdk why am I having to do >> this? any ideas >> >> >> 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 Fri, Aug 1, 2014 at 8:29 AM, David DeMizio <[email protected]> wrote: >> >>> Hello, >>> >>> I attempted to create an image revision this morning and it got to the >>> point where it was trying to reload and failed with error below. any ideas >>> on what might be causing this. I believe in the past it was due to a >>> datastore being offline but I don't see any datastores offline. >>> >>> vmwarelinux-VCLLAB0142-v1 does not exist on management node and could >>> not be retrieved >>> ------------------------------------------------------------------------ >>> time: 2014-08-01 08:19:41 >>> caller: new.pm:reload_image(639) >>> ( 0) new.pm, reload_image (line: 639) >>> (-1) new.pm, process (line: 291) >>> (-2) vcld, make_new_child (line: 571) >>> (-3) vcld, main (line: 350) >>> ------------------------------------------------------------------------ >>> management node: <my server> >>> reservation PID: 31992 >>> parent vcld PID: 25140 >>> >>> request ID: 9 >>> reservation ID: 9 >>> request state/laststate: reload/inuse >>> request start time: 2014-08-01 08:19:35 >>> request end time: 2014-08-01 08:49:35 >>> for imaging: no >>> log ID: none >>> >>> computer: vdi-n-001 >>> computer id: 4 >>> computer type: virtualmachine >>> computer eth0 MAC address: 00:50:56:00:A0:10 >>> computer eth1 MAC address: <undefined> >>> computer private IP address: 10.10.14.101 >>> computer public IP address: 10.10.13.139 >>> computer in block allocation: no >>> provisioning module: VCL::Module::Provisioning::VMware::VMware >>> >>> vm host: <my host> >>> vm host ID: 2 >>> vm host computer ID: 9 >>> vm profile: VMware vCenter >>> vm profile VM path: /vmfs/volumes/VCL-WORKSPACE >>> vm profile repository path: <undefined> >>> vm profile datastore path: /vmfs/volumes/VCL-MASTER >>> vm profile disk type: shared >>> >>> image: vmwarelinux-VCLLAB0142-v1 >>> image display name: VCLLAB01 >>> image ID: 42 >>> image revision ID: 60 >>> image size: 11306 MB >>> use Sysprep: yes >>> root access: yes >>> image owner ID: 1 >>> image owner affiliation: Local >>> image revision date created: 2014-08-01 08:13:14 >>> image revision production: no >>> OS module: VCL::Module::OS::Linux >>> image revision comments: added xrdp >>> >>> user: vclreload >>> user name: vcl reload >>> user ID: 2 >>> user affiliation: Local >>> ------------------------------------------------------------------------ >>> RECENT LOG ENTRIES FOR THIS PROCESS: >>> |31992|9:9|reload| : "value" => "datastore-44" >>> |31992|9:9|reload| : }, 'ManagedObjectReference' ), >>> |31992|9:9|reload| : "freeSpace" => "290769076224", >>> |31992|9:9|reload| : "maintenanceMode" => "normal", >>> |31992|9:9|reload| : "multipleHostAccess" => 0, >>> |31992|9:9|reload| : "name" => "vdi-esx-2", >>> |31992|9:9|reload| : "normal_path" => "/vmfs/volumes/vdi-esx-2", >>> |31992|9:9|reload| : "type" => "VMFS", >>> |31992|9:9|reload| : "url" => >>> "ds:///vmfs/volumes/52b38ee1-05bf5992-02de-a0d3c1046268/" >>> |31992|9:9|reload| : }, 'DatastoreSummary' ) >>> |31992|9:9|reload| : } >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|VMware.pm:get_vmx_base_directory_path(3094)|determined >>> vmx base directory path: /vmfs/volumes/VCL-WORKSPACE >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|VMware.pm:_get_datastore_names(6792)|datastore >>> names: >>> |31992|9:9|reload| VCL-MASTER >>> |31992|9:9|reload| VCL-WORKSPACE >>> |31992|9:9|reload| VDI-BOOT >>> |31992|9:9|reload| VDI-BOOT2 >>> |31992|9:9|reload| VDI-VMFS01 >>> |31992|9:9|reload| VDI-VMFS02 >>> |31992|9:9|reload| VIEW-WORKSPACE >>> |31992|9:9|reload| vcl_master >>> |31992|9:9|reload| vcl_workspace >>> |31992|9:9|reload| vdi-esx-1 >>> |31992|9:9|reload| vdi-esx-2 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|vSphere_SDK.pm:file_exists(1973)|file (datastore >>> root) exists: [VCL-WORKSPACE] >>> 2014-08-01 08:19:37|31992|9:9|reload|VMware.pm:is_vm_dedicated(4257)|VM >>> disk mode does not need to be dedicated >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|VMware.pm:get_vmdk_base_directory_path_shared(3566)|using >>> VM profile datastore path as the vmdk base directory path: >>> /vmfs/volumes/VCL-MASTER >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|VMware.pm:_get_datastore_names(6792)|datastore >>> names: >>> |31992|9:9|reload| VCL-MASTER >>> |31992|9:9|reload| VCL-WORKSPACE >>> |31992|9:9|reload| VDI-BOOT >>> |31992|9:9|reload| VDI-BOOT2 >>> |31992|9:9|reload| VDI-VMFS01 >>> |31992|9:9|reload| VDI-VMFS02 >>> |31992|9:9|reload| VIEW-WORKSPACE >>> |31992|9:9|reload| vcl_master >>> |31992|9:9|reload| vcl_workspace >>> |31992|9:9|reload| vdi-esx-1 >>> |31992|9:9|reload| vdi-esx-2 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|vSphere_SDK.pm:file_exists(1973)|file (datastore >>> root) exists: [VCL-MASTER] >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|Module.pm:create_provisioning_object(525)|VCL::Module::Provisioning::VMware::VMware >>> provisioner object created for vdi-n-001, address: 43748a0 >>> 2014-08-01 08:19:37|31992|9:9|reload|State.pm:initialize(154)|returning 1 >>> 2014-08-01 08:19:37|31992|9:9|reload|vcld:make_new_child(568)|VCL::new >>> object created and initialized >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:is_parent_reservation(1004)|returning >>> true: parent reservation ID for this request: 9 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2436)|attempting >>> to retrieve current state of computer vdi-n-001 from the database >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2467)|retrieved >>> current state of computer vdi-n-001 from the database: reload >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:_automethod(847)|data structure >>> updated, hash path: >>> $self->request_data->{reservation}{9}{computer}{state}{name}, data >>> identifier: computer_state_name, data: >>> |31992|9:9|reload| : "reload" >>> 2014-08-01 08:19:37|31992|9:9|reload|utils.pm:is_inblockrequest(5761)|zero >>> rows were returned from database select >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2436)|attempting >>> to retrieve current state of computer vdi-n-001 from the database >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2467)|retrieved >>> current state of computer vdi-n-001 from the database: reload >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:_automethod(847)|data structure >>> updated, hash path: >>> $self->request_data->{reservation}{9}{computer}{state}{name}, data >>> identifier: computer_state_name, data: >>> |31992|9:9|reload| : "reload" >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|new.pm:computer_not_being_used(742)|retrieving >>> info for reservations assigned to vdi-n-001 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|utils.pm:get_connect_method_info(10060)|attempting >>> to retrieve connect method info: >>> |31992|9:9|reload| imagerevision: 60 - vmwarelinux-VCLLAB0142-v1 >>> |31992|9:9|reload| OS: 36 - vmwarelinux >>> |31992|9:9|reload| OS type: 2 - linux >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|utils.pm:get_connect_method_info(10124)|ssh: >>> connectmethodid=1, OStypeid=2, OSid=NULL, imagerevisionid=NULL, disabled=0 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|utils.pm:get_connect_method_info(10124)|RDP: >>> connectmethodid=2, OStypeid=2, OSid=NULL, imagerevisionid=NULL, disabled=0 >>> 2014-08-01 08:19:37|31992|9:9|reload|utils.pm:get_user_info(7541)|UID >>> value is not configured for user vclreload, setting UID to VCL user ID: >>> vclreload, standalone: 1 >>> 2014-08-01 08:19:37|31992|9:9|reload|utils.pm:get_user_info(7541)|UID >>> value is not configured for user vclreload, setting UID to VCL user ID: >>> vclreload, standalone: 1 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|utils.pm:get_request_by_computerid(5992)|retrieved >>> info and DataStructure object for 9:9 >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|new.pm:computer_not_being_used(755)|vdi-n-001 >>> is not assigned to any other reservations >>> 2014-08-01 08:19:37|31992|9:9|reload|new.pm:process(127)|vdi-n-001 is >>> not being used >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2436)|attempting >>> to retrieve current state of computer vdi-n-001 from the database >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:get_computer_state_name(2467)|retrieved >>> current state of computer vdi-n-001 from the database: reload >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|DataStructure.pm:_automethod(847)|data structure >>> updated, hash path: >>> $self->request_data->{reservation}{9}{computer}{state}{name}, data >>> identifier: computer_state_name, data: >>> |31992|9:9|reload| : "reload" >>> 2014-08-01 08:19:37|31992|9:9|reload|new.pm:reload_image(511)|calling >>> VCL::Module::Provisioning::VMware::VMware->node_status() >>> 2014-08-01 08:19:37|31992|9:9|reload|utils.pm:insertloadlog(3666)|inserted >>> computer=4, statuscheck, checking status of node >>> 2014-08-01 >>> 08:19:37|31992|9:9|reload|VMware.pm:node_status(1152)|attempting to check >>> the status of computer vdi-n-001, image: vmwarelinux-VCLLAB0142-v1 >>> 2014-08-01 >>> 08:19:38|31992|9:9|reload|OS.pm:is_ssh_responding(653)|vdi-n-001 is NOT >>> responding to SSH, ports 22 or 24 are both closed >>> 2014-08-01 08:19:38|31992|9:9|reload|VMware.pm:node_status(1189)|VM >>> vdi-n-001 is not responding to SSH, returning 'RELOAD' >>> 2014-08-01 08:19:38|31992|9:9|reload|new.pm:reload_image(526)|node_status >>> returned a hash reference >>> 2014-08-01 08:19:38|31992|9:9|reload|new.pm:reload_image(531)|node_status >>> hash reference contains key {status}=RELOAD >>> 2014-08-01 08:19:38|31992|9:9|reload|new.pm:reload_image(576)|request >>> state is reload, node will be reloaded regardless of status >>> 2014-08-01 08:19:38|31992|9:9|reload|new.pm:reload_image(608)|node >>> status is reload, vdi-n-001 will be reloaded >>> 2014-08-01 08:19:38|31992|9:9|reload|utils.pm:insertloadlog(3666)|inserted >>> computer=4, loadimageblade, vdi-n-001 must be reloaded with >>> vmwarelinux-VCLLAB0142-v1 >>> 2014-08-01 08:19:38|31992|9:9|reload|new.pm:reload_image(622)|calling >>> VCL::Module::Provisioning::VMware::VMware->does_image_exist() >>> 2014-08-01 >>> 08:19:38|31992|9:9|reload|VMware.pm:get_vmdk_base_directory_path_shared(3566)|using >>> VM profile datastore path as the vmdk base directory path: >>> /vmfs/volumes/VCL-MASTER >>> 2014-08-01 >>> 08:19:39|31992|9:9|reload|vSphere_SDK.pm:_get_file_info(2520)|searching for >>> matching file paths: base directory path: '[VCL-MASTER] >>> vmwarelinux-VCLLAB0142-v1', search pattern: 'vmwarelinux-VCLLAB0142-v1.vmdk' >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|vSphere_SDK.pm:_get_file_info(2575)|retrieved >>> info for 0 matching files: >>> |31992|9:9|reload| : {} >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|vSphere_SDK.pm:find_files(2120)|matching file >>> count: 0 >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|vSphere_SDK.pm:file_exists(1992)|file does not >>> exist: [VCL-MASTER] vmwarelinux-VCLLAB0142-v1/vmwarelinux-VCLLAB0142-v1.vmdk >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|VMware.pm:does_image_exist(4595)|image does not >>> exist in the shared directory on the VM host >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|VMware.pm:get_repository_vmdk_base_directory_path(4140)|repository >>> path is not configured in the VM profile >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|VMware.pm:get_repository_vmdk_directory_path(4181)|image >>> repository vmdk directory path cannot be determined because repository path >>> is not configured in the VM profile >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|VMware.pm:does_image_exist(4601)|image does not >>> exist on the VM host and image repository path is not configured in the VM >>> profile >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|new.pm:reload_image(629)|vmwarelinux-VCLLAB0142-v1 >>> does not exist on this management node >>> 2014-08-01 08:19:41|31992|9:9|reload|new.pm:reload_image(633)|calling >>> VCL::Module::Provisioning::VMware::VMware->retrieve_image() >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|Provisioning.pm:retrieve_image(278)|image >>> retrieval skipped, image library functions are disabled for this management >>> node >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|DataStructure.pm:get_computer_private_ip_address(1641)|attempting >>> to retrieve private IP address for computer: vdi-n-001 >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|OS.pm:get_file_contents(1897)|retrieved 29 lines >>> from file on vcl: '/etc/hosts' >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|DataStructure.pm:get_computer_private_ip_address(1697)|returning >>> IP address from /etc/hosts file: 10.10.14.101 >>> 2014-08-01 08:19:41|31992|9:9|reload|utils.pm:is_inblockrequest(5761)|zero >>> rows were returned from database select >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|DataStructure.pm:get_image_affiliation_name(2121)|image >>> owner id: 1 >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|DataStructure.pm:retrieve_user_data(1412)|attempting >>> to retrieve and store data for user: user.id = '1' >>> 2014-08-01 >>> 08:19:41|31992|9:9|reload|DataStructure.pm:retrieve_user_data(1475)|data >>> has been retrieved for user: admin (id: 1) >>> >>> >>> >> >
