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.
Description of problem:
When a system is registered through a capsule, it subsequently shows up the Satellite's content hosts UI. However, there is no indication as to which systems are connected to capsules, if any and which those capsules are.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150303.0
How reproducible:
Steps to Reproduce:
1. Register n number of clients to satellite; assure some of these are subscribed directly and some are through a capsule
2. Go to content hosts UI
3. Try to identify which systems are connected to capsules (or which those capsule are)
Actual results:
No differentiation indicating which clients are connected to which capsules.
Expected results:
Ability to make said determination
Additional info:
* Probably would want associated CLI functionality as well.
* Not sure what else you might use this for. filter hosts based on parent capsule, etc? Unsure.
*** Bug 1374977 has been marked as a duplicate of this bug. ***
Comment 12Renzo Nuccitelli
2017-03-30 14:02:56 UTC
I have tested this on sat 6.2.9. snap 1. I followed links until finding the name of field on UI:
https://github.com/Katello/katello/pull/6211/files#diff-a7de84d2632e4182751dd164e8665548R65
So I registered a Content Host to Satellite itself and navigated to host detail and got no match for "Registered Through" search on UI. Maybe this change is not yet cherry picked. So I am moving this back to assigned.
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