Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 :(
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?
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.
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.
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.
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.
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.