Bug 1377408

Summary: cpu_socket and lscpu.socket are not reported via API for hypervisors
Product: Red Hat Satellite Reporter: Andrea Perotti <aperotti>
Component: FactAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.2CC: aperotti, bbuckingham, bcourt, bkearney, daniele, dlobatog, jcallaha, ktordeur
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 18:04:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1353215    

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.