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:
Traceback in production.log while registering Satellite content host with insights.

Version-Release number of selected component (if applicable):
- Satellite 6.10.0 snap 10
- tfm-rubygem-foreman_rh_cloud-4.0.24.1-1.el7sat.noarch

How reproducible:
- Always

Steps to Reproduce:
1. Import manifest, create activation key.
2. Go to Hosts > All Hosts > Click on Register Host
3. Generate command to register a content host(make sure "Setup Insights" is set to yes)
4. Register content host using the gerated command.

Actual results:
- Traceback in satellite production.log

Expected results:
- No traceback while registering satellite content host with insights.

Additional info:

*** Bug 1941465 has been marked as a duplicate of this bug. ***

Verified:

Verified with:
- Satellite 6.10.0 snap 20
- tfm-rubygem-foreman_rh_cloud-4.0.26-1.el7sat.noarch

Test steps:
1. Import manifest, create activation key.
2. Go to Hosts > All Hosts > Click on Register Host
3. Generate command to register a content host(make sure "Setup Insights" is set to yes)
4. Register content host using the gerated command.

Observation:
- No traceback while registering satellite content host with insights.

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 (Moderate: Satellite 6.10 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-2021:4702