-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: Discovery 7.0.2
-
Component/s: Assets Discovery
-
None
-
1
-
Severity 3 - Minor
Issue Summary
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Set up and environment to scan hosts and virtual cpu details with discovery.
- Discovery scan doesn’t capture CPUCOUNT for virtual_guest object in version 7.02
Expected Results
We should see cpucount tag for virtualguest
<VirtualGuestInfo> <ObjectHash>F5162B37059D6C5701667660509F039A</ObjectHash> <Name>ad-windows-server-2016-esxi</Name> <State>poweredOn</State> <RAM>4096</RAM> <UUID>564d621f-70b4-6b30-1498-640322752e02</UUID> <ConfigurationFile>[ad-datastore] ad-windows-server-2016-esxi/ad-windows-server-2016-esxi.vmx</ConfigurationFile> <GuestType>VMware VM</GuestType> <CPUCount>2</CPUCount>
Actual Results
There is no <CPUCount> tag in the scan
<VirtualGuestInfo> <ObjectHash>F5162B37059D6C5701667660509F039A</ObjectHash> <Name>ad-windows-server-2016-esxi</Name> <State>poweredOff</State> <RAM>4096</RAM> <UUID>564d621f-70b4-6b30-1498-640322752e02</UUID> <ConfigurationFile>[ad-datastore] ad-windows-server-2016-esxi/ad-windows-server-2016-esxi.vmx</ConfigurationFile> <GuestType>VMware VM</GuestType> <OS> <ObjectHash>10A076C3DC479D243708E3ADACF6711A</ObjectHash> <OSName>Microsoft Windows Server 2016 (64-bit)</OSName> </OS> <CPUs> <CPUInfo> <ObjectHash>7D56D0FC01D2F697738738A4D9ED41A3</ObjectHash> <DeviceID>vmCPU0</DeviceID> <CPUType>Virtual CPU</CPUType> <CoresPerProcessor>1</CoresPerProcessor> <MaxCPUSpeed>0</MaxCPUSpeed> <NumberOfLogicalProcessors>0</NumberOfLogicalProcessors> </CPUInfo> <CPUInfo> <ObjectHash>D064A377738D6D70C01286B85947ED1D</ObjectHash> <DeviceID>vmCPU1</DeviceID> <CPUType>Virtual CPU</CPUType> <CoresPerProcessor>1</CoresPerProcessor> <MaxCPUSpeed>0</MaxCPUSpeed> <NumberOfLogicalProcessors>0</NumberOfLogicalProcessors> </CPUInfo> </CPUs> </VirtualGuestInfo>
Workaround
N/A
- relates to
-
JSMAD-460 Loading...