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:
Since XenServer is not one of the supported hypervisors as per the Virtual Instances Guide. Ideally in the downstream, we should remove this from the drop down menu list under Satellite Web UI -> Infrastructure -> Virt-who configs -> New Virt-who Config -> Hypervisor Type drop down menu. 


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


How reproducible:
100% 


Steps to Reproduce:
1. Go to Satellite Web UI -> Infrastructure -> Virt-who configs -> New Virt-who Config 
2. Under Hypervisor Type, use the drop down and you will see the XenServer
3. 

Actual results:
XenServer (xen) is listed as Hypervisor Type. 


Expected results:
Since it's not supported hypervisor, we should not include it. 


Additional info:

Hello Team, 

This is visible on Satellite 6.4.1 as well.

Even Red Hat Satellite 6.3.5 has that option.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32247 has been resolved.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702