[
https://issues.apache.org/jira/browse/CLOUDSTACK-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-3529.
----------------------------------------------
Resolution: Fixed
> Unable to test file existence due to exception java.lang.RuntimeException
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3529
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3529
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Environment: Cloudstack over VMware ESXi 5.0
> ACS master commit 1f004f60e8542b7e6f75a780b59ad738161f7346
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> While deploying VM seeing RuntimeException.
> This is not blocking VM deployment.
> 2013-07-15 12:33:23,564 INFO [vmware.mo.DatastoreMO]
> (DirectAgent-288:10.102.192.2) Folder ROOT-13-18 does not exist on datastore
> 2013-07-15 12:33:23,564 INFO [storage.resource.VmwareStorageProcessor]
> (DirectAgent-288:10.102.192.2) creating linked clone from template
> 2013-07-15 12:33:25,942 INFO [storage.resource.VmwareStorageProcessor]
> (DirectAgent-288:10.102.192.2) Move volume out of volume-wrapper VM
> 2013-07-15 12:33:26,183 INFO [storage.resource.VmwareStorageProcessor]
> (DirectAgent-288:10.102.192.2) detach disks from volume-wrapper VM ROOT-13-18
> 2013-07-15 12:33:28,899 INFO [storage.resource.VmwareStorageProcessor]
> (DirectAgent-288:10.102.192.2) destroy volume-wrapper VM ROOT-13-18
> 2013-07-15 12:33:29,202 INFO [vmware.mo.DatastoreMO]
> (DirectAgent-288:10.102.192.2) Search file on
> [20cd70ee163932ecaedf8541162dc393] ROOT-13-18
> 2013-07-15 12:33:31,243 INFO [vmware.mo.DatastoreMO]
> (DirectAgent-288:10.102.192.2) Unable to test file existence due to exception
> java.lang.RuntimeException, skip deleting of it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
