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:
In 6.1 you could get the UUID (or name) of whoever registered the system in /katello/api/systems/:id in the "registered_by" field. This was really useful for looking for systems reported by a specific virt-who instance.

This is gone in the new unified hosts structure. I'd like the feature back if possible :)


Version-Release number of selected component (if applicable):
6.2.8

How reproducible:
100%

Steps to Reproduce:
1. GET /api/v2/hosts/:id

Actual results:
no "registered_by" field

Expected results:
"registered_by" field in the host object directly or in the subscription_facet

Additional info:

After investigation, this is being provided by bug 1380117; therefore, I am going to close this one as a duplicate.  If there are any concerns, please do let us know.  Thanks!

Note: in the updated API, the registered_by user will be included within

subscription_facet_attributes -> user, where user can include id & login

*** This bug has been marked as a duplicate of bug 1380117 ***