Bug 1394388 - Activation Key returning all systems under associations tab
Summary: Activation Key returning all systems under associations tab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.2.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Peter Ondrejka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1372826
Blocks: CEE_Sat6_Top_BZs, GSS_Sat6_Top_Bugs
TreeView+ depends on / blocked
 
Reported: 2016-11-11 20:19 UTC by Bryan Kearney
Modified: 2021-08-30 13:35 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1372826
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15347 0 None None None 2016-11-11 20:19:26 UTC
Red Hat Knowledge Base (Solution) 2599871 0 None None None 2016-11-11 20:19:26 UTC

Comment 2 Peter Ondrejka 2016-11-22 09:52:02 UTC 
Verified in Satellite 6.3 snap 6, associations of the activation key now display the correct list of content hosts.
Comment 10 Andrew Kofink 2017-03-09 13:19:02 UTC 
Didn't mean to clear this needsinfo. See above.
Comment 14 John Mitsch 2017-03-29 12:27:36 UTC 
Andrew and Ashfaqur,

This BZ is a bit confusing as it is a clone, and the original problem has been fixed. It seems like there is a new problem with the columns being empty in the activation key content host associations tab (which I was able to reproduce). I think we should open that up in a separate (not cloned) bugzilla and track it there.

-John
Comment 15 Ashfaqur Rahaman 2017-04-03 23:14:29 UTC 
Hi John,

There is already another bug : 

https://bugzilla.redhat.com/show_bug.cgi?id=1415009

Agreed with you. lets continue on the other bug. 

Thanks
Ash
Comment 17 Satellite Program 2018-02-21 16:54:37 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:0336
Note You need to log in before you can comment on or make changes to this bug.