Bug 1421817 - product content not listed under subscription "product content"
Summary: product content not listed under subscription "product content"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: jcallaha
URL:
Whiteboard:
Depends On: 1376512
Blocks: 1334863
TreeView+ depends on / blocked
 
Reported: 2017-02-13 18:35 UTC by jcallaha
Modified: 2019-08-12 14:36 UTC (History)
6 users (show)

Fixed In Version: tfm-rubygem-katello-3.0.0.105-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1376512
Environment:
Last Closed: 2017-03-06 15:12:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
verification screenshot (154.86 KB, image/png)
2017-02-28 20:44 UTC, jcallaha
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16568 0 None None None 2017-02-13 18:35:17 UTC

Comment 3 Satellite Program 2017-02-13 19:02:25 UTC
Upstream bug assigned to tomckay

Comment 4 Satellite Program 2017-02-13 19:02:28 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16568 has been resolved.

Comment 5 jcallaha 2017-02-28 20:43:44 UTC
Verified in Satellite 6.2.8 snap 4.

You can now see the provided product content for both RH and custom subscriptions. See attached for verification screenshot.

Comment 6 jcallaha 2017-02-28 20:44:02 UTC
Created attachment 1258494 [details]
verification screenshot

Comment 7 Bryan Kearney 2017-03-06 15:12:20 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/RHBA-2017:0447


Note You need to log in before you can comment on or make changes to this bug.