Sign Up for the Quarterly Newsletter

ESXi Arm Edition

Log In to Comment

Open

#31 vSAN witness issue

  • Damon Hawkins • Nov 18, 2020

    A fresh build:
    two node NUC (NUC8i7BEH) cluster running 7.0.1, 17119627
    vCenter 7.0.1.00100, 17004997
    VDS
    Pi 4, 8GB, 7.0.0, 17068872

    When creating a two host VSAN cluster, the witness host running on the Pi fails with the following:

    2020-11-18T02:23:00.988Z INFO vsan-mgmt[13750] [VsanPyVmomiProfiler::logProfile opID=1e1b62c3] invoke-method:ha-vsan-stretched-cluster-system:GetStretchedClusterCapability: 0.03s:pi01.xxxx.co.uk
    2020-11-18T02:23:01.021Z INFO vsan-mgmt[13750] [VsanPyVmomiProfiler::logProfile opID=1e1b62c3] invoke-method:ha-vsan-health-system:QueryVersion: 0.03s:pi01.xxxx.co.uk
    2020-11-18T02:23:01.021Z ERROR vsan-mgmt[13750] [VsanVcStretchedClusterSystemImpl::ConvertToStretchedCluster opID=1e1b62c3] Failed to configure a stretched cluster:
    2020-11-18T02:23:01.022Z ERROR vsan-mgmt[13750] [VsanVcStretchedClusterSystemImpl::ConvertToStretchedCluster opID=1e1b62c3] (vmodl.fault.ManagedObjectNotFound) {
    msg = '',
    obj = 'vim.host.VsanHealthSystem:ha-vsan-health-system'
    }
    Traceback (most recent call last):
    File "/build/mts/release/bora-17004997/bora/build/vcenter/release/pkg/vsanmgmt/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcStretchedClusterSystemImpl.py", line 2472, in ConvertToStretchedCluster
    File "/build/mts/release/bora-17004997/bora/build/vcenter/release/pkg/vsanmgmt/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcStretchedClusterSystemImpl.py", line 1330, in _PreCheckGetWitnessInfo
    File "/build/mts/release/bora-17004997/bora/build/vcenter/release/pkg/vsanmgmt/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcStretchedClusterSystemImpl.py", line 1502, in _GetHostVsanHealthVersion
    File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 592, in <lambda>
    self.f(*(self.args + (obj,) + args), **kwargs)
    File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 381, in _InvokeMethod
    return self._stub.InvokeMethod(self, info, args)
    File "/build/mts/release/bora-17004997/bora/build/vcenter/release/pkg/vsan-health/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanPyVmomiProfiler.py", line 413, in InvokeMethod
    File "/build/mts/release/bora-17004997/bora/build/vcenter/release/pkg/vsan-health/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanHostHelper.py", line 512, in InvokeMethod
    File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1875, in InvokeMethod
    raise obj
    PyCppVmomi.vmodl.fault.ManagedObjectNotFound: (vmodl.fault.ManagedObjectNotFound) {
    msg = '',
    obj = 'vim.host.VsanHealthSystem:ha-vsan-health-system'
    }

  • vMan • Nov 18, 2020

    glad to see I am not the only one.

    I have built a whole new vCenter, vSAN cluster, etc... and i have the same problem as you. Bug #30

  • tobeee • Nov 18, 2020

    same issue here
    2 MSI Nucs + RPI

    first tried Vcenter 7 U1

    then 7.0.0.10700

    and Pi 4, 8GB, 7.0.0, 17068872
    with Standard Switch
    also with diffrent usb sticks

    no luck at all :(

  • William Lam • Nov 19, 2020

    ESXi-Arm is based on vSphere 7.0, this means for setting up vSAN Witness, you need to ensure both VC/ESXi-x86 match. I just deployed this using the latest ESXi-Arm Build (17068872) it works as expected.

    I've also updated my blog post to explicitly mention the supported builds:

    VCSA 7.0d 16620007
    VCSA 7.0c 16749653

    ESXi 7.0 15843807
    ESXi 7.0b 16324942

  • tobeee • Nov 20, 2020

    Thanks William

    Now it's working also with build
    VCSA 7.0d 16620013

  • vMan • Nov 20, 2020

    I completely reinstalled my vCenter, 2 x86 hosts and the Pi... still getting the same error.

    Task: vSAN operation precheck

    (vmodl.fault.ManagedObjectNotFound) {
    msg = '',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) [],
    obj = 'vim.host.VsanHealthSystem:ha-vsan-health-system'
    }

    vCenter Server Appliance Version:7.0.0.10700 Build number 16749653

    Pi is on 17068872

    Hypervisor: VMware ESXi, 7.0.0, 16324942

    The pi has the correct vmware-fdm vib...

    vmware-fdm 7.0.0-16620014 VMware VMwareCertified 2020-09-01

    Honestly at this point I am like ??? any ideas?

  • Rob • Nov 20, 2020

    Got the "Failed to extract requested data. Check vSphere Client logs for details." when adding the Raspberry Pi as the witness. VCenter is 7.0.0.10700(d) Build number 16749653.

  • Damon Hawkins • Nov 21, 2020

    I have blown everything away and re-tested with:
    both VCSA 16620013 and 6749653
    16324942 on the ESXi cluster hosts
    ARM 17068872

    I still cannot get this to work, as seen by Rob, I get "Failed to extract requested data. Check vSphere Client logs for details." when adding the witness."
    In the logs:

    VsanVcStretchedClusterSystemImpl::ConvertToStretchedCluster opID=6e25819f] (vmodl.fault.ManagedObjectNotFound) {
    msg = '',
    faultCause = <unset>,
    faultMessage = (vmodl.LocalizableMessage) [],
    obj = 'vim.host.VsanHealthSystem:ha-vsan-health-system'
    }