Bug 1983575

Summary:	Insights recommendations sync task fails for first time on fresh satellite installation with "RestClient::BadRequest: 400 Bad Request".
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	RH Cloud - Inventory	Assignee:	Shimon Shtein <sshtein>
Status:	CLOSED ERRATA	QA Contact:	Silas Pusateri <spusater>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	aruzicka, jjeffers, osousa, pcreech, zhunting
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_rh_cloud-4.0.26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1986125 (view as bug list)		Environment:
Last Closed:	2021-11-16 14:12:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jameer Pathan 2021-07-19 07:03:31 UTC

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.

Comment 4 Jameer Pathan 2021-08-17 08:00:00 UTC

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.

Comment 6 Silas Pusateri 2021-10-27 13:05:01 UTC

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

Comment 9 errata-xmlrpc 2021-11-16 14:12:49 UTC

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