Hi, this is probably a formatting issue in the VMmark3.properties file. Could you post the results folder (named using the RunName parameter in VMmark3.properties) from /~/VMmark3/provisioning-output so I can take a look?
I can consistently create clusters where all the VMs come to life – or appear to (screenshot VMmark setup below).
In the test environment, cluster creation works for both “static” and “dhcp” test setups.
Have also tried extending the time limits in “VMmark3.properties” for RebootTimeSeconds and for ProvisionPingIpSeconds.
Logs (example attached) consistently show that the arrangement isn’t really working, even while the VMs continue to come online.
It always ends like this:
2018-10-01T20:48:17.377 [pool-3-thread-1] ERROR MAIN : Exception Caught: Provision targetDatastore Null VM Exception : Review Log and Configuration : Unable to locate targetDatastore: 'static-SUT1-datastore' in Datacenter : exitSetting true
2018-10-01T20:48:17.394 [pool-3-thread-1] INFO MAIN : Email Disabled
2018-10-01T20:48:17.394 [pool-3-thread-1] INFO MAIN : Ending Early
Have also tried using vSAN storage - One-Host and Two-Host - but setup takes much longer.
And with the same result.
Any help would be greatly appreciated.