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.
What data is the customer looking for? Just Host Collections? So far we are planning to import the following items from Satellite:
Lifecycle Environment
Content View
Activation Key
Capsule
Host Collection
Location
Organization
Parameters
Host Group
Comment 19Tasos Papaioannou
2021-02-17 15:48:41 UTC
Verified on 6.9.0 snap 13.
1.) With an Insights client registered through Satellite, create and upload an inventory report to cloud.redhat.com:
- Configure > Inventory Upload
- click on the organization name, then on 'Restart'.
2.) Verify that the 'Generating' and 'Uploading' columns both display checkmarks.
3.) Log in to cloud.redhat.com/insights and click on Inventory.
4.) Verify that the client is present, and that the icon in the 'Tags' column is clickable.
5.) Verify that the tags are present and accurate, e.g.,
location tpapaioa-location satellite
content_view Default Organization View satellite
organization Default Organization satellite
activation_key tpapaioa-key satellite
host_collection tpapaioa-host-collection satellite
host_collection tpapaioa-host-collection-2 satellite
organization_id 1 satellite
lifecycle_environment Library satellite
satellite_instance_id XXXXXXXXXXXXXX satellite
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.9 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:1313