SDDC Manager workload domain update tab gives following warning "Unable to compute applicability for drift Creates a Distributed Virtual Port Group to enable traffic isolation between management VMs and ESXi hosts."
search cancel

SDDC Manager workload domain update tab gives following warning "Unable to compute applicability for drift Creates a Distributed Virtual Port Group to enable traffic isolation between management VMs and ESXi hosts."

book

Article ID: 410733

calendar_today

Updated On:

Products

VMware SDDC Manager VMware Cloud Foundation

Issue/Introduction

  • SDDC Manager workload domain update tab gives following warning

    Unable to compute applicability for drift Creates a Distributed Virtual Port Group to enable traffic isolation between management VMs and ESXi hosts

     

  • Error in /var/log/vmware/vcf/domainmanager/domainmanager.log
    DEBUG [vcf_dm,68c##############4b,be45] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-7]  Handler Error Response: {"errorCode":"FAILED_TO_FETCH_APPLICABLE_DRIFTS_CONFIGURATION_REALIZED_CHECK_FAILED","arguments":["Creates a Distributed Virtual Port Group to enable traffic isolation between management VMs and ESXi hosts","[bf00####-####-####-####-########dee4]"],"message":"Unable to compute applicability for drift Creates a Distributed Virtual Port Group to enable traffic isolation between management VMs and ESXi hosts. Because configuration realized check failed on resources [bf00####-####-####-####-########dee4].","remediationMessage":"Please check logs and fix the failures of drift configuration realized checks. Then restart the service to trigger the configuration realized checks again and re-try the API. If this does not resolve the issue, please contact GSS.","referenceToken":"V####Q"}

     

    ERROR [vcf_dm,0000000000000000,0000] [c.v.v.c.c.c.DvpgConfigurationDriftCheck,ForkJoinPool.commonPool-worker-751]  Unhandled exception in DVPGConfigurationDriftCheck isConfigurationRealized for resource bf00####-####-####-####-########dee4.
    com.vmware.vim.vmomi.client.exception.VmomiProtocolException: https://vcenter.example.com:443/sdk invocation failed with "com.vmware.vim.vmomi.core.exception.MarshallException: Missing value for managed object reference"
            at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:265)
    
    Caused by: com.vmware.vim.vmomi.core.exception.MarshallException: Missing value for managed object reference

Environment

VMware Cloud Foundation

Cause

This issue is caused when MOB_ID of vDS (virtual Distributed Switch)  is not present or incorrect in the sddc manager database.

Resolution

  1. Take snapshot of SDDC Manager VM
  2. SSH to SDDC Manager VM with vcf user and su to root
  3. Find the VDS id mapped to the cluster id (bf00####-####-####-####-########dee4) as reported in the log
    psql -h localhost -U postgres -d platform -c "\x" -c "select cluster_id,vds_id from cluster_and_vds where cluster_id='bf00####-####-####-####-########dee4'"

    Sample output

    -[ RECORD 1 ]------------------------------------
    cluster_id | bf00####-####-####-####-########dee4
    vds_id     | 1484####-####-####-####-########4ceb

     

  4. Check the VDS details in SDDC manager database
    psql -h localhost -U postgres -d platform -c "\x" -c "select id,name,source_id from vds where id='<vds_id from step#3>'

    Sample

    psql -h localhost -U postgres -d platform -c "\x" -c "select id,name,source_id from vds where id='1484####-####-####-####-########4ceb'"

    Sample output

    id                 | 1484####-####-####-####-########4ceb
    name               | sample-vds01
    source_id          | 

    Note: source_id is missing here

  5. Update the source id
    1. Find the mob id for the vds
      1. Open vCenter in vSphere client
      2. Click on Network icon
      3. Select the VDS sample-vds01
      4. Check the URL in browser address bar to locate the dvs id

        Sample
        https://vcenter.example.com/ui/app/dvs;nav=n/urn:vmomi:VmwareDistributedVirtualSwitch:dvs-21:5288####-####-####-####-########546f/summary

        Note: here dvs id is dvs-21

    2. Update the dvs id in vds table in sddc manager database
      psql -h localhost -U postgres -d platform -c "update vds set source_id='<dvs id from step#5(a)(iv)> where id='<vds_id from step#3>'"

      Sample

      psql -h localhost -U postgres -d platform -c "update vds set source_id='dvs-21' where id='1484####-####-####-####-########4ceb'"
  6. Restart all the services on the SDDC manager
    /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh