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.

Created attachment 1687730 [details]
patch to add a macro to allow access to registered_at in safe mode

Description of problem:
There is no macro defined to access host_subscription_facet(host)&.registered_at from a custom report while safe mode is enabled (default).

Version-Release number of selected component (if applicable):
tfm-rubygem-katello-3.14.0.20-1.el7sat

How reproducible:
Always

Steps to Reproduce:
1. Clone "Entitlements" report template
2. Try to add a column reporting the registration date of hosts
3.

Actual results:
Safemode doesn't allow to access 'registered_at' on #<Safemode::ScopeObject>

Expected results:
Customers can include the registration date of hosts in their custom reports.

Additional info:

Upstream bug assigned to wclark

Upstream bug assigned to wclark

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29743 has been resolved.

Verified with Sat 6.8 snap 6.0.

All *content* hosts' registration datetimes can be accessed by "registered_at(host)". This doesn't work for non-content hosts which is expected, according to devel.

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 (Important: Satellite 6.8 release), 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-2020:4366