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.
Found in nightly
Reproduce:
1. Have a Katello with virt-who subscriptions
2. Navigate to Content -> Subscriptions
Actual:
All the "Requires Virt-Who" column shows a dash ("-").
Expected:
Repositories which support virt-who unlimited guest subscriptions should have a check in the "Requires Virt-Who" column.
Notes:
See attached screenshots.
The virt-who unlimited guest subscriptions are shown in the 'Actual behavior' screenshot, which is correct. This is shown when there's a hypervisor consuming one of the physical subscriptions of a virt-who supported subscription.
The API seems to be returning the correct value, and the show page of a single subscription properly reports the virt-who support, so it should just be a UI change.
virt-who isn't actually required for these subscriptions, just supported, so I'm not sure why the column is titled "Requires Virt-Who", but it's like that in old versions of Katello (i.e. 3.4.z).
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, 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-2018:2927
Found in nightly Reproduce: 1. Have a Katello with virt-who subscriptions 2. Navigate to Content -> Subscriptions Actual: All the "Requires Virt-Who" column shows a dash ("-"). Expected: Repositories which support virt-who unlimited guest subscriptions should have a check in the "Requires Virt-Who" column. Notes: See attached screenshots. The virt-who unlimited guest subscriptions are shown in the 'Actual behavior' screenshot, which is correct. This is shown when there's a hypervisor consuming one of the physical subscriptions of a virt-who supported subscription. The API seems to be returning the correct value, and the show page of a single subscription properly reports the virt-who support, so it should just be a UI change. virt-who isn't actually required for these subscriptions, just supported, so I'm not sure why the column is titled "Requires Virt-Who", but it's like that in old versions of Katello (i.e. 3.4.z).