i'm using the vmmark 3.0 to test on server
when I started to provision the first tile(which is tile0) from the vmmark template
the terminal always show the following error message:
ERROR MAIN : Exception Caught: Provision targetDatastore Null VM Exception : Review Log and Configuration : Unable to locate targetDatastore: 'vsanDatastore' in Datacenter : exitSetting true
the provision target data store was set to just only one storage(which is vsanDatastore)
the vcenter credential and other settings(IP, domain, email, tiles...) don't seem to be wrong.
and no other error messages, just this one.
i found some of the VMs can be created randomly after several provisioning tries.
(maybe 9 or 13 or 17...VMs can be cloned from the template)
but this first-tile-provision just never success.
the vmmark3.properties and the output result log are attached.
does anyone know about this issue?
i've checked the vmkernel.log and no any errors in any test hosts.
jamesz08 thanks for your advice!
actually, i just solved my issue a minute ago.
it seemed that the provisioning datastore of client VM cannot be placed with other VMs(DS3, Auction, Elastic...etc) together.
i set the provisioning datastore of all the VMs in the same storage(vsanDatastore, under the test cluster) so failed again and again...
i succeed the first tile provisioning by changing the client's datastore to other place(on client cluster host that it should be).
Can you run again with DebugLevel = 3 and post the results?
okay...I just did and still failed(ending early) although there are 19 VMs cloned from the template.
the error message is the same one:unable to locate targetDatastore: 'vsanDatastore'
i've attached the vmmark3.properties file and provisioningservice.log file.
by the way,
my test cluster hosts are using SAS control card because my target vsan capacity tier utilizes SAS HDD
all the SAS card driver and firmware were updated to specified version which matched the VMware Compatibility Guide
despite there seemed to be a version glitch on one of the hosts but this shouldn't be the problem, as shown in figure attached.
Can you check vmkernel.log on your hosts for any errors?
I would suggest removing the 10.101.6.5 host from your cluster and trying again to rule out any configuration issues. Those warnings indicate some problem.
i've checked the vmkernel.log and no any errors in any test hosts.
jamesz08 thanks for your advice!
actually, i just solved my issue a minute ago.
it seemed that the provisioning datastore of client VM cannot be placed with other VMs(DS3, Auction, Elastic...etc) together.
i set the provisioning datastore of all the VMs in the same storage(vsanDatastore, under the test cluster) so failed again and again...
i succeed the first tile provisioning by changing the client's datastore to other place(on client cluster host that it should be).