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.
Description of problem:
Add a rake task so that you can register your satellite and bind your org to the hybrid cloud environment.
Version-Release number of selected component (if applicable):
Satellite 6.11
How reproducible:
Steps to Reproduce:
1. Get token from hybrid cloud env
2. Run rake task and provide token
3. Get success message upon org binding
Tested by spinning up a Satellite locally on libvirt and doing the following:
1. On the Satellite, execute `org_id=3 SATELLITE_RH_CLOUD_URL=https://$mtls_auth_domain /usr/sbin/foreman-rake rh_cloud:hybridcloud_register`.
2. On the client, execute `insights-client --register`
3. On the sat, perform an inventory upload, an inventory sync, and fetch insights recommendations.
4. On an arbitrary client, query Inventory and verify the host is present (`insights-client --register` worked) with a populated list of facts (Satellite inventory upload worked).
5. On the client, execute `insights-client --unregister`
This was done with an HTTP proxy in place, in the form `http://user:pass@domain:port`. After registering the Satellite to the test hybrid cloud environment, I also extracted a cert and key from the Satellite's manifest, and made some direct API calls with curl.
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 (Satellite 6.11.5.2 Async Bug Fix Update), 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/RHBA-2023:1478