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:
currently, there are some servers using the same insights-id and we are unable to track this out. adding this information on rh_cloud plugin will be easy to track the duplicated ones and help the customer to fix this out on the customer side.

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

How reproducible:
100%

Steps to Reproduce:
1. create a new inventory report
2. extract the files
3. check the json_file

Actual results:
no insights_id

Expected results:
insights_id as part of the data

Additional info:

Verified.
Version Tested: Satellite 6.10 snap 15

Steps Followed:

1. Register a host to insights and add it to Satellite
2. Confirm host facts are included by running 'subscription-manager repos --list' on that host. (The insights ID is not included unless host facts are enabled.)
3. Create a new inventory report
4. Download and extract the files
5. Check the json file

Observation:
The insights ID is included in the data

Additional Info:

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