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

Discovery scan does not retrieve the right number of VCPUs vs CPUs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 3.0.10
    • Assets Discovery
    • None

      Issue Summary

      Discovery scan does not retrieve the right number of VCPUs vs CPUs

      Steps to Reproduce

      1. enable Windows patterns (WMI or PS)
      2. set Discovery to scan Windows hosts where CPUs number is different than VCPUs number
      3. observe that the commands executed for both patterns:

        WMIQuery
        Windows_CPUs.pat
        SELECT * FROM Win32_Processor

        and

        PowerShellExecute
        Windows_CPUs_PS.pat
        Get-WmiObject Win32_Processor

      Are always retrieving the same number of CPUs and VCPUs even if number of VCPUs is different as we can see in Windows device management system info.

      This goes for several different Win versions.

      Expected Results

      The command executed should retrieve the correct number of VCPUs

      Actual Results

      The command executed do not retrieve the correct number of VCPUs

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDSERVER-10966] Discovery scan does not retrieve the right number of VCPUs vs CPUs

            Nancy Freeman added a comment -

            All set - ticket reopened and pdf with screenshots attached

            Nancy Freeman added a comment - All set - ticket reopened and pdf with screenshots attached

            Tiziana Marchionni added a comment -

            Hi dc0f8c52539d,

            Would you please help by attaching those files to your relevant case here SDS-64311 or raise a new one so that our devs can double check in relationship to your last comment?

            Thanks for your collaboration!

            Best,

            Tiziana

            Tiziana Marchionni added a comment - Hi dc0f8c52539d , Would you please help by attaching those files to your relevant case here SDS-64311 or raise a new one so that our devs can double check in relationship to your last comment? Thanks for your collaboration! Best, Tiziana

            Nancy Freeman added a comment -

            JSM is not allowing me to upload / attach anything

            Nancy Freeman added a comment - JSM is not allowing me to upload / attach anything

            vgedzhev (Inactive) added a comment - - edited

            Hello dc0f8c52539d ,

            Unfortunately I can't see the screenshots. Could you try to re-upload them again?

             

            vgedzhev (Inactive) added a comment - - edited Hello dc0f8c52539d , Unfortunately I can't see the screenshots. Could you try to re-upload them again?  

            Nancy Freeman added a comment -

            Adding better pics - same vm on VMWare and HyperV

             

            Nancy Freeman added a comment - Adding better pics - same vm on VMWare and HyperV  

            Nancy Freeman added a comment -

            The insight interface shows CPU Count and CPU type.  When looking at a VMWare guest scanned via Vcenter it returns the accurate quantity of VCPU Count and CPU Type (See Example 1)   - Where your answer may be technically accurate it is not correct.    HyperV returns a incorrect CPU count and the correct CPU Type (Example 2) 

            Example 1 VMWare:  

             

             

            Example 2 HyperV:

            Nancy Freeman added a comment - The insight interface shows CPU Count and CPU type.  When looking at a VMWare guest scanned via Vcenter it returns the accurate quantity of VCPU Count and CPU Type (See Example 1)   - Where your answer may be technically accurate it is not correct.    HyperV returns a incorrect CPU count and the correct CPU Type (Example 2)  Example 1 VMWare:        Example 2 HyperV:

            vgedzhev (Inactive) added a comment -

            This is not a bug. We actually don't return virtual/logical cores count at all. Could be more or less easily implemented as a small new feature.

            vgedzhev (Inactive) added a comment - This is not a bug. We actually don't return virtual/logical cores count at all. Could be more or less easily implemented as a small new feature.

              8a797fe2b442 vgedzhev (Inactive)
              tmarchionni@atlassian.com Tiziana Marchionni
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: