VMmark4.1 - Error when provisioning: [ERROR]: opID[1] VMmark-4.1.0-224 get_vm_object Datacenter obj None

[schris14]

I upgraded my VMmark4 installation to 4.1 and attempted an initial provisioning to only one host in my SUT cluster.  These are the informational and error messages I get....

root@primeclient:~/VMmark4# vmmark4service --mode provision --properties /root/VMmark4/VMmark4.properties --time_zone US/Arizona
2026-05-13 13:38:53,894 [vmmark4service MainThread] [INFO]: vmmark4service: 1.1.18
2026-05-13 13:38:53,894 [vmmark4service MainThread] [INFO]: Connecting to vCenter (vMOMI): '10.61.48.100'
2026-05-13 13:38:53,918 [vmmark4service MainThread] [INFO]: Testing PrimeClient Connectivity for '198.18.4.251'
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]:   STAF PING SUCCESS for '198.18.4.251'
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]: PrimeClient Connectivity Test Passed
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]: Provisioning Mode active for 0 tiles and vmtype provisioning_mode
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]:   provision path ='/root/VMmark4/provision/Provision-2026051354'
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]:
Namespace(mode='provision', properties='/root/VMmark4/VMmark4.properties', vm_name='', vm_username='root', vm_password='vmmark4', primeclient_ip='198.18.4.251', vcenter_ip='10.61.48.100', vcenter_username='[e-mail]', vcenter_password='Tie@pwd714', datacenter='Hardware-Benchmarking', cluster='SUT', client_cluster='VMmark4', workload_spec='/root/VMmark4/source/workload-spec.json', auto_workload_config='/root/VMmark4/tools/auto_workload_config.py', workload_list='Standby,DS35DB,DS35WebA,DS35WebB,DS35WebC,AuctionWebA,AuctionWebB,AuctionWebC,AuctionWebDNosql,AuctionWebEDB,AuctionWebF,AuctionAppA,AuctionAppB,AuctionAppC,AuctionKA,AuctionKB,AuctionKC,AuctionKD,SocialNetwork,NoSQLBenchA,NoSQLBenchB,NoSQLBenchC', infrastructure_list='vmotion,svmotion,xvmotion,deploy', datastore='DS35DB:DS-NVME-1,DS35WebA:DS-NVME-1,DS35WebB:DS-NVME-1,DS35WebC:DS-NVME-1,AuctionWebA:DS-NVME-1,AuctionWebB:DS-NVME-1,AuctionWebC:DS-NVME-1,AuctionWebDNosql:DS-NVME-1,AuctionWebEDB:DS-NVME-1,AuctionWebF:DS-NVME-1,AuctionAppA:DS-NVME-1,AuctionAppB:DS-NVME-1,AuctionAppC:DS-NVME-1,AuctionKA:DS-NVME-3,DS-NVME-4,AuctionKB:DS-NVME-3,DS-NVME-4,AuctionKC:DS-NVME-4,DS-NVME-3,AuctionKD:DS-NVME-4,DS-NVME-3,NoSQLBenchA:DS-NVME-1,NoSQLBenchB:DS-NVME-1,NoSQLBenchC:DS-NVME-1,SocialNetwork:DS-NVME-1,Standby:DS-NVME-1', client_datastore='DS-NVME-2', infra_datastore='', deploy_vminfo='DeployVM0:198.18.4.246', deploy_templates='', sut_host_name='', client_host_name='', sut_host_password='', client_host_password='', provisioning_mode='vmtype', provisioning_source='VMmark-4.1.0-224', provisioning_ip_mode='Static', provisioning_ip_gateway='198.18.4.251', provisioning_ip_subnetmask='255.255.0.0', provisioning_ip_dnsserver_list='8.8.8.8,8.8.8.4', provisioning_ip_dnssuffix_list='eng.vmware.com,eng.vmware.com', static_ip='', static_ip_startaddress='198.18.4.1', static_ip_endaddress='245', time_zone='US/Arizona', domain='vmware', num_cpu=4, num_mem=8192, extra_disk='', resource_pool='', vm_folder='', network_label='Private Network', network_switch_type='dvswitch', management_network_label='', management_network_switch_type='standard', runtime_seconds=120, num_processes=8, rmq_operation='', rmq_message='', output_file='', iteration_number=0, sleep_seconds=30, sleep_time=30, tile_number='0', starting_tile_number=1, max_ssh_tries=20, max_ip_seconds=600, max_misc_tries=30, extra_disk_mode='thin', ping_check=True, max_duration_seconds='960', no_progress_bar=False, sustainability_power='/root/VMmark4/tools/misc/sustainability_power.py', tile_state='on', quick_start_options='', concurrent_operations=1, slack_webhook='', gchat_webhook='', webhook_message_subject='', webhook_message_state='', webhook_message_content='', results_directory='/root/VMmark4/provision/Provision-2026051354', log_level='INFO', default_path='/root/VMmark4/', version=None, ntp_max_drift='10', csi_datastore='DS-NVME-3,DS-NVME-4', advanced_provisioning_file='', ovftool='', ova='', ova_source_network='', drs_state='', ignore_deployova_errors=False, deployova_power_state='on', gateway='', subnetmask='', make_nfs='/root/VMmark4/tools/make-nfs.sh', nfs_vm_basename='nfs-server', nfs_datastore_name='vmmark4_nfs_datastore', max_postprovision_ping_tries='10', ds35db_size='10', ds35db_stores='10', ptd='0', ptd_ramp_time='1800', ptd_clients='', ptd_targets='Server', ptd_coms='', ptd_ports='', ptd_meter_types='', ptd_volt_ranges='120', ptd_amp_ranges='5.0', ptd_local_hostnames='', ptd_local_ports='')
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]: Checking VMmark Template VM object: VMmark-4.1.0-224
2026-05-13 13:38:54,189 [vmmark4service MainThread] [INFO]: Connecting to vCenter (vMOMI): '10.61.48.100'
2026-05-13 13:38:54,210 [vmmark4service MainThread] [ERROR]: opID[1] VMmark-4.1.0-224 get_vm_object Datacenter obj None
2026-05-13 13:38:54,210 [vmmark4service MainThread] [ERROR]: VM VMmark-4.1.0-224 not found
2026-05-13 13:38:54,210 [vmmark4service MainThread] [INFO]: check_template_vm identified issues with provisioning_source
2026-05-13 13:38:54,210 [vmmark4service MainThread] [INFO]: Checking Host NTP settings
2026-05-13 13:38:54,215 [vmmark4service MainThread] [ERROR]: Check Host NTP Datacenter obj None
Traceback (most recent call last):
  File "/tmp/onefile_6584_1778704733_724574/vmmark4service.py", line 2930, in <module>
  File "/tmp/onefile_6584_1778704733_724574/vmmark4service.py", line 392, in provision
  File "/tmp/onefile_6584_1778704733_724574/vmmark4service.py", line 2023, in check_host_ntp
AttributeError: 'NoneType' object has no attribute 'hostFolder'

Any help will be appreciated.  Thank you.

-------------------------------------------

Attachment(s)

VMmark4.properties.txt   18 KB 1 version

[Joshua Schnee]

Hi schris14

From the log here, it seems the datacenter 'Hardware-Benchmarking' wasn't found within your vCenter.  You may want to double check the spelling and try again.

-------------------------------------------

[schris14]

Joshua,

Thank you for your response.  I have verified the spelling in vCenter and within the VMmark4.properties file and they match.  I even updated the Datacenter name to 'HB' in both places to ensure the name would not be misspelled and I get the same error.

Can you recommend any other troubleshooting steps?

Thank you in advance.

-------------------------------------------

[schris14]

-------------------------------------------

[schris14]

Vcenter section of the VMmark4.properties file

# vSphere Settings #vsphere
# This section details the connection settings for the vCenter Server (vCServer) under test.
#
# String vCServer : Default empty : Ex: 10.115.155.239 : vCenter Server IP or hostname
vCServer = x.x.x.x
# String vCServerUsername : Default [e-mail] : Ex vCServerUsername = [e-mail]
vCServerUsername = [e-mail]
# String vCServerPassword : Default empty : Ex vCServerPassword = vmware
vCServerPassword = xxxxxxxxxxxxx
# String vCServerDatacenter : Default empty : Ex vCServerDatacenter = Datacenter
vCServerDatacenter = HB
# String vCServerVMmark4Cluster : Default empty : Ex vCServerVMmark4Cluster = Cluster1 : This is the SUT cluster of hosts
#    running your VMmark4 workload VMs and is where provisioning will place new workload VMs.
vCServerVMmark4Cluster = SUT
# String vCServerClientCluster : Default empty : Ex vCServerClientCluster = ClientCluster1 : This is the Client cluster of hosts
#    running your client VMs and is where provisioning will place new client VMs.
#    Note that this should be a different cluster than the SUT cluster.
vCServerClientCluster = VMmark4

-------------------------------------------

[Joshua Schnee]

Can you do the following:

1. Upload a results folder
2. Take a larger screenshot of your vSphere environment, including the URL bar of your browser

To create a results zip file:

• Change directories to the ~/VMmark/results folder
• Create a zip file of your last attempt.  Ex: zip -r Result-2026051217-details.zip Result-2026051217-details
• Add to this thread and I'll take a look

-------------------------------------------

[schris14]

Joshua,

Here is the screenshot.

[Screenshot 2026-05-15 at 10.28.39 AM.png]



There is nothing in the results directory. The issue I am having is in provisioning the Tiles.

root@primeclient:~/VMmark4/results# pwd;ls -la
/root/VMmark4/results
total 24
drwxr-xr-x 3 root root 4096 May 13 12:08 .
drwxr-xr-x 10 root root 4096 May 15 09:39 ..
drwx------ 2 root root 16384 May 13 12:08 lost+found

Thank you.

STEPHEN CHRISTENSEN | SENIOR INFRASTRUCTURE ENGINEER II

CORE INFRASTRUCTURE – COMPUTE ENGINEERING

AMERICAN EXPRESS, COLLEAGUE SINCE '98

18850 N 56th Street | Phoenix, AZ 85054

Mobile: [phone] E: [e-mail]<mailto:[e-mail]>


Upcoming PTO: Friday May 22nd - Monday May 1st

[Joshua Schnee]

For some reason that screenshot didn't come through.  Can you try again?

As far as additional logs wrt to provisioning

Please create a full provisioning bundle by doing the following:
1. If you used a VMmark4 properties file, please add it to the most recent Provision-* folder that was created at ~/VMmark4/provision.  This should be the latest one in your folder.
2. Make sure the vmmark4service-output.log from provisioning/quick_start attempt is added to the  same Provision-* folder 
3. Copy or create a shell script that shows the command you used to request VMmark4 provisioning/quick_start to run and add this to the same Provision-* folder 
4. Zip the Provision-* folder and attach it here.

-------------------------------------------

[schris14]

-------------------------------------------

[schris14]

Joshua,

Thank you for you time.  You forced me to review my setup a few more times and your earlier assessment was correct.  The datacenter did not exist in vCenter.  My team recently created a new vCenter to account for a separation for Storage and Compute engineers....and I was using the old IP address in the VMmark4.properties file.  If I had used the new FQDN of the vCenter I would have caught this a few days ago.

I restarted my provisioning ..and I get past this error but run into another one.

Would you like me to open a new thread for the new error or keep uploading artifacts to this thread?

-------------------------------------------

[Joshua Schnee]

Hi,

No worries, glad we were able to resolve that issue. As for your next one, either option is fine. 

-------------------------------------------

[schris14]

Information uploaded in file name vmmark4.tar.gz

-------------------------------------------

Attachment(s)

vmmark4.tar.gz   11 KB 1 version

[Joshua Schnee]

Hi,

Looks like the issue is that you have "ProvisioningNumTiles = 0".  You should set this to 1 if you want to create one tile.

-------------------------------------------

[schris14]

Joshua,

That was the problem. I am now able to provision Tile0.

Thank you for the help.


STEPHEN CHRISTENSEN | SENIOR INFRASTRUCTURE ENGINEER II

CORE INFRASTRUCTURE – COMPUTE ENGINEERING

AMERICAN EXPRESS, COLLEAGUE SINCE '98

18850 N 56th Street | Phoenix, AZ 85054

Mobile: [phone] E: [e-mail]<mailto:[e-mail]>