Bug 1606420

Summary: "Requires Virt-Who" column incorrect in new Subscriptions UI
Product: Red Hat Satellite Reporter: Andrew Kofink <akofink>
Component: Subscription ManagementAssignee: Walden Raines <walden>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: cwelton, ehelms, walden
Target Milestone: 6.4.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:33:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Kofink 2018-07-20 19:54:46 UTC
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).

Comment 1 Andrew Kofink 2018-07-20 19:54:50 UTC
Created from redmine issue https://projects.theforeman.org/issues/24335

Comment 2 Andrew Kofink 2018-07-20 19:54:53 UTC
Upstream bug assigned to None

Comment 5 Brad Buckingham 2018-07-24 14:03:16 UTC
Moving to POST since the upstream PR has been merged.

Comment 9 Bryan Kearney 2018-10-16 19:33:29 UTC
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