VMware Flings Flings

May 16, 2022

you did not specify the SD section, meaning no device was specified, please refer to vdbench manual or hit ADD button in HCIBench.

Hi Team, I have an account for a vCenter which have two datastore (vsanDatastore for management & WorkloadDatastore for customer use). My account can only access WorkloadDatastore, and when we using HCIBench for testing, we specify the 'WorkloadDatastore' as Datastore name in the profile page and save the configs and start the validation, the validation process will report an error like this:

'/usr/lib/ruby/2.5.0/json/common.rb:156:in 'parse': 765: unexpected token at" (JSON::ParserError)
from /usr/lib/ruby/2.5.0/json/common.rb:156:in 'parse'
from /opt/automation/lib/rvc-util:rb:647:in '_get_vsan_stats'
from /opt/automation/lib/rvc-util:rb:654:in '_get_vsan_default_policy'
from /opt/automation/lib/pre-validation.rb:227:in 'block in validate_vsan_info'
from /opt/automation/lib/pre-validation.rb:225:in 'each'
from /opt/automation/lib/pre-validation.rb:227:in 'validate_vsan_info'
from /opt/automation/lib/pre-validation.rb:609:in ' '

does this caused by the HCIBench checking the vsanDatastore accessible? Could you please give us some advise. Thanks.

is this on VMC environment? we've seen that before but we did not figure out the root cause. we will take a look at that in the VMC env and get back to you as soon as we have a solution.

Thanks for you quick response. Yes, it is on VMC environment.

aethervisor

I am getting the same issue btw. If I comment out the section in the prevalidation ruby for line 609, it passes validation, but the actual testing just says Testing Finished right away.

I tried 2.5.3 and it validates fine, but it has the same behavior when trying to run the test.

Mar 23, 2022

i did a quick test and got it fixed, please replace the file in HCIBench /opt/automation/lib/rvc-util.rb with https://github.com/vsphere-tmm/HCIBench/blob/master/rvc_rvc/lib/rvc/modules/vsantest/automation/lib/rvc-util.rb
and try again.

Mar 28, 2022

Sorry for the delay feedback, we spent some time to resolve the inter-connectivity error, and finally ran the validation process passed. Your hot fix update is ok for resolving the vasan checking error. Thanks for your great help.

Mar 23, 2022

Thanks Wei for quickly fixing it. I'll try it and get your back soon.

XiaoHui Chew

Feb 27, 2022

2022-02-28 07:07:10 +0000: Validating Fio binary and the workload profiles...
2022-02-28 07:07:10 +0000: Validating VC IP and Credential...
2022-02-28 07:07:14 +0000: VC IP and Credential Validated
2022-02-28 07:07:14 +0000: Validating Datacenter DC01...
2022-02-28 07:07:14 +0000: Datacenter DC01 Validated
2022-02-28 07:07:14 +0000: Validating Cluster MGMT...
2022-02-28 07:07:14 +0000: Cluster MGMT Validated
2022-02-28 07:07:14 +0000: Cluster MGMT has DRS mode: partiallyAutomated
2022-02-28 07:07:14 +0000: Validating If Any Hosts in Cluster MGMT for deployment is in Maintainance Mode...
2022-02-28 07:07:15 +0000: All the Hosts in Cluster MGMT are not in Maitainance Mode
2022-02-28 07:07:15 +0000: Validating Host esxi01.officelab.com IP Address...
2022-02-28 07:07:19 +0000: Host esxi01.officelab.com Address Validated
2022-02-28 07:07:19 +0000: Validating If Host esxi01.officelab.com Is In Cluster MGMT...
2022-02-28 07:07:19 +0000: Host esxi01.officelab.com Is In Cluster MGMT
2022-02-28 07:07:19 +0000: Validating Host esxi02.officelab.com IP Address...
2022-02-28 07:07:23 +0000: Host esxi02.officelab.com Address Validated
2022-02-28 07:07:23 +0000: Validating If Host esxi02.officelab.com Is In Cluster MGMT...
2022-02-28 07:07:23 +0000: Host esxi02.officelab.com Is In Cluster MGMT
2022-02-28 07:07:23 +0000: Validating Network DPortGroup-VLAN47...
2022-02-28 07:07:23 +0000: Network DPortGroup-VLAN47 Validated, type is DistributedVirtualPortgroup
2022-02-28 07:07:23 +0000: Checking If Network DPortGroup-VLAN47 is accessible from all the hosts for deployment...
2022-02-28 07:07:24 +0000: Network DPortGroup-VLAN47 is accessible from all the hosts for deployment
2022-02-28 07:07:24 +0000: Datastore vsanDatastore Validated
2022-02-28 07:07:24 +0000: Checking Datastore vsanDatastore type...
2022-02-28 07:07:24 +0000: Datastore vsanDatastore type is vsan
2022-02-28 07:07:24 +0000: Getting Datastore vsanDatastore id...
2022-02-28 07:07:24 +0000: Checking If Datastore vsanDatastore is accessible from any of the hosts of MGMT...
2022-02-28 07:07:24 +0000: Datastore vsanDatastore is accessible from hosts esxi01.officelab.com, esxi02.officelab.com
2022-02-28 07:07:26 +0000: vSAN is Enabled in Cluster MGMT, the vSAN Datastore for test is vsanDatastore
2022-02-28 07:07:27 +0000: vSAN Local Datastore name is vsanDatastore, capacity is 1199 GB and freespace is 837 GB, the default policy is vSAN Default Storage Policy
2022-02-28 07:07:27 +0000: Validating storage policy vSAN Default Storage Policy...
2022-02-28 07:07:28 +0000: Validating IP pool availability...
2022-02-28 07:07:55 +0000: Validating cluster inter-connectivity...
"SocketError: getaddrinfo: Temporary failure in name resolution"
"SocketError: getaddrinfo: Temporary failure in name resolution"
2022-02-28 07:08:38 +0000: Cluster inter-connectivity validated
2022-02-28 07:08:38 +0000: Easy RUN Enabled, Skipping Validating VM and Parameter Config...
2022-02-28 07:08:38 +0000: ------------------------------------------------------------------------------
2022-02-28 07:08:38 +0000: All the config has been validated, please go ahead to kick off testing
2022-02-28 07:08:38 +0000: ------------------------------------------------------------------------------
Error: option '--path' needs a parameter.
Try --help for help.
Error: option '--path' needs a parameter.
Try --help for help.
Error: option '--path' needs a parameter.
Try --help for help.

2022-02-28 07:12:27 +0000: Set vSAN Performance Service to verbose mode in cluster MGMT
2022-02-28 07:12:34 +0000: Setting vSAN Performance Service interval to 60s on esxi01.officelab.com
2022-02-28 07:12:35 +0000: vSAN Performance Service interval is set to 60s on Performance Service master node: esxi01.officelab.com
2022-02-28 07:12:54 +0000: Deployment Started.
2022-02-28 07:13:25 +0000: [ERROR] Unknown Failed...
2022-02-28 07:13:25 +0000: VMs Preserved for Debugging Purpose, You Can Run /opt/automation/cleanup-vm.sh to Delete VMs Manually
2022-02-28 07:13:25 +0000: Testing Failed, For Details Please Find Logs in /opt/automation/logs
2022-02-28 07:13:25 +0000: Please Cancel And Re-Run The Testing

/opt/automation/logs/deploy.log
2022-02-28 07:13:25 +0000: Unable to connect ESXi host

I tried to SSH from HCI Appliance to all ESXi hosts and it is working fine but i am getting the above errors when trying to
start the test.

XiaoHui Chew

Feb 27, 2022

After rebooting the appliance, now it seems to work. Please ignore previous message.

Adam Tomczyk

Feb 17, 2022

Can someone tell me what is wrong? my host vs23ff is most def. in the FF-Cluster, any idea how to fix this?

2022-02-17 21:35:29 +0000: Validating Fio binary and the workload profiles...
2022-02-17 21:35:29 +0000: Validating VC IP and Credential...
2022-02-17 21:35:33 +0000: VC IP and Credential Validated
2022-02-17 21:35:33 +0000: Validating Datacenter FF-datacenter...
2022-02-17 21:35:33 +0000: Datacenter FF-datacenter Validated
2022-02-17 21:35:33 +0000: Validating Cluster FF-Cluster...
2022-02-17 21:35:33 +0000: Cluster FF-Cluster Validated
2022-02-17 21:35:33 +0000: Cluster FF-Cluster has DRS mode disabled
2022-02-17 21:35:33 +0000: Validating If Any Hosts in Cluster FF-Cluster for deployment is in Maintainance Mode...
2022-02-17 21:35:33 +0000: All the Hosts in Cluster FF-Cluster are not in Maitainance Mode
2022-02-17 21:35:33 +0000: Validating Host vs23ff IP Address...
2022-02-17 21:35:37 +0000: Host vs23ff.corp.kearnyfederalsavings.net Address Validated
2022-02-17 21:35:37 +0000: Validating If Host vs23ff Is In Cluster FF-Cluster...
2022-02-17 21:35:37 +0000: ------------------------------------------------------------------------------
2022-02-17 21:35:37 +0000: Host vs23ff.corp.kearnyfederalsavings.net Is NOT In Cluster FF-Cluster!
2022-02-17 21:35:37 +0000: ------------------------------------------------------------------------------
govc: ServerFaultCode:
Error processing attribute "type" with value ""

while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312

while parsing property "obj" of static type ManagedObject

while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301

while parsing property "objectSet" of static type ArrayOfObjectSpec

while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219

while parsing call information for method CreateFilter
at line 2, column 66

while parsing SOAP body
at line 2, column 60

while parsing SOAP envelope
at line 2, column 0

while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0