Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11113

Wrong UUID is scanned from vCenter to InsightDiscovery

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 3.1.2
    • 4.21.2
    • Assets Discovery
    • None

    Description

      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); }

      Attachments

        Activity

          People

            8a797fe2b442 vgedzhev (Inactive)
            6f6f0ed1241f Shiwani Choudhary
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Backbone Issue Sync