Wrong UUID is scanned from vCenter to InsightDiscovery

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 3.1.2
    • Affects Version/s: 4.21.2
    • Component/s: Assets Discovery
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      While scanning vCenter with InsightDiscovery (ESXI_VirtualMachines.pat). The UUID returned for a VM is incorrect, which is shown in the vCenter GUI nor inside the VM (wmic bios get serialnumber).

      Steps to Reproduce

      1. Use ESXI_VirtualMachines.pat to scan from vCenter.

      Expected Results

      UUID returned is correct

      Actual Results

      UUID returned is wrong

      ...

      Workaround

      The workaround is provided by One of our customers 

      A quick fix in the file ESXi_VirtualMachines.pat :
      // if (!string.IsNullOrEmpty(vim.Config.InstanceUuid))
      //

      { // vmGuest.UUID = vim.Config.InstanceUuid; // LogService.Instance.LogDebug("Set UUID based on Config.InstanceUuid: " + vim.Config.InstanceUuid); // }

      // else
      //

      { // LogService.Instance.LogDebug("VM UUID not available for: " + vim.Name); // }

      if (vim.Config.Uuid != null)

      { vmGuest.UUID = vim.Config.Uuid; LogService.Instance.LogDebug("Set UUID based on Config.Uuid: " + vim.Config.Uuid); }

      else

      { LogService.Instance.LogDebug("VM UUID not available for: " + vim.Name); }

            Assignee:
            vgedzhev (Inactive)
            Reporter:
            Shiwani Choudhary
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: