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:
Insights recommendations sync task fails for first time on fresh satellite installation with "RestClient::BadRequest: 400 Bad Request".

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

How reproducible:
- Always

Steps to Reproduce:
1. Install Satellite 6.10.0 snap 9
2. Register a satellite content host with insights.
3. Go to Configure > Insights
4. Add RH Cloud token and click on sync recommendation button.

Actual results:
- The "Insights full sync" task fails with "RestClient::BadRequest: 400 Bad Request".

Expected results:
- The "Insights full sync" task finishes successfully and insights recommendations are shown. 

Additional info:
- This only happens the first time user tries to sync recommendations after adding the RH Cloud token. It works on second attempt.

FailedQA:

Tested with:
- Satellite 6.10.0 snap 13
- tfm-rubygem-foreman_rh_cloud-4.0.25.1-2.el7sat.noarch

Observation:
On satellite UI we no longer see "RestClient::BadRequest: 400 Bad Request" but in satellite production.log 
we are getting "400 Bad Request (RestClient::BadRequest)" while trying to save RH cloud token.

Based on discussion with Shim around the traceback in production.log, moving this bz back to assigned state.

Verified:

Tested with:
Satellite 6.10.0 snap 23

Observation:
The recommendations sync succeeds the first time and no error message can be found in the logs

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