Bug 1431232

Summary: [RFE] please expose "type" data of the host
Product: Red Hat Satellite Reporter: Evgeni Golov <egolov>
Component: Hosts - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.8CC: bbuckingham, bkearney, daniele, dconsoli, egolov, jcallaha, ktordeur, rjerrido
Target Milestone: UnspecifiedKeywords: FutureFeature, PrioBumpPM, Reopened
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1647003 1647762 (view as bug list) Environment:
Last Closed: 2020-04-13 17:25:20 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1647003, 1647762, 1650573    

Description Evgeni Golov 2017-03-10 16:40:37 UTC 
Description of problem:
In 6.1 you could get the type (Hypervisor, Virtual Guest, etc) of the system in /katello/api/systems/:id in the "type" field. This was really useful for looking for systems that were Hypervisros or Guests.

This is gone in the new unified hosts structure. I'd like the feature back if possible :)


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

How reproducible:
100%

Steps to Reproduce:
1. GET /api/v2/hosts/:id

Actual results:
no "type" field

Expected results:
"type" field in the host object

Additional info:
it seems this data is not even in the "hosts" table of foreman :(
Comment 1 Brad Buckingham 2017-03-21 18:57:20 UTC 
In Satellite 6.2, the UI appears to be using the following host attributes to display type:

e.g. 

{
  "facts": {
    "virt::host_type": "kvm",
     ...
  }
}

While the wording may be different (i.e. not specifically 'Hypervisor', 'Virtual Guest'...etc), would this be sufficient?
Comment 2 Evgeni Golov 2017-03-21 21:30:21 UTC 
Hi Brad,

sadly no. This is a subscription-manager submitted fact. As there is no subscription-manager on ESXi hypervisors, this fact is not set there at all.
Comment 3 Bryan Kearney 2018-10-03 19:19:36 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 5 Bryan Kearney 2018-11-01 14:44:58 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is  not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 7 Bryan Kearney 2018-11-30 14:50:53 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 8 Bryan Kearney 2019-11-05 18:46:24 UTC 
*** Bug 1635861 has been marked as a duplicate of this bug. ***
Comment 10 Rich Jerrido 2020-04-13 17:25:20 UTC 
This BZ was opened prior to virt-who reporting hypervisior sockets and facts. It has done this since around Satellite 6.3. If one wishes to determine if a node is a hypervisor, it is expected to use the system's facts.