Bug 1377408 - cpu_socket and lscpu.socket are not reported via API for hypervisors
Summary: cpu_socket and lscpu.socket are not reported via API for hypervisors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Fact
Version: 6.2.2
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1353215
TreeView+ depends on / blocked
 
Reported: 2016-09-19 15:24 UTC by Andrea Perotti
Modified: 2021-09-09 11:56 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:04:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1307024 0 high CLOSED Rebase virt-who in Satellite 6 Streams (was) virt-who needs to report facts about the hypervisors 2021-09-09 11:46:37 UTC

Internal Links: 1307024

Description Andrea Perotti 2016-09-19 15:24:53 UTC 
Description of problem:
Calling API to know the full infos on a system, the Satellite answer lack of the socket information if the host is an hypervisor:

https://mysatellite/katello/api/v2/systems/0db5881b-1dc1-4cb7-a16c-4c1f74f0aefa?fields=full


Version-Release number of selected component (if applicable):
Satellite 6.2.2

How reproducible:
Always

Actual results:
Missing infos about sockets in the json answer:

Expected results:
lscpu.socket(s)
cpu.cpu_socket(s)
Comment 2 Barnaby Court 2018-02-22 18:34:27 UTC 
In Satellite 6.3,  cpu.cpu_socket(s) is reported by virt-who for esx, hyperv, libvirt, and rhevm hypervisors. 

Is that sufficient?
Comment 3 Andrea Perotti 2018-03-02 10:41:19 UTC 
Hi Barnaby,
           that info is positive that is reported by virt-who, but is sat6 able to store it and expose it back via api?
Comment 7 Bryan Kearney 2018-09-04 18:04:03 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.