Bug 1939834 - 400 BadRequest from the server on registering host to insights.
Summary: 400 BadRequest from the server on registering host to insights.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Inventory
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.0
Assignee: Shimon Shtein
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks: 1931390
TreeView+ depends on / blocked
 
Reported: 2021-03-17 07:29 UTC by Jameer Pathan
Modified: 2021-04-21 13:26 UTC (History)
3 users (show)

Fixed In Version: 3.0.18.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:26:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_rh_cloud pull 517 0 None open Forward also content-type to insights-client forwarding code 2021-03-17 07:29:52 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:26:54 UTC

Comment 2 Jameer Pathan 2021-03-22 08:24:54 UTC 
Verified:

Verified with:
- Satellite 6.9.0 snap 18
- tfm-rubygem-foreman_rh_cloud-3.0.18.1-1.el7sat.noarch

Test steps:
1. Register a host to the Satellite.
2. Try registering host to insights.(insights-client --register)
3. See production.log during insights-client registration.

Observation:
- No "400 BadRequest" error in production.log while registering host to insights.
- "404 Not Found" in production.log while registering host to insights. Filed BZ#1941465
Comment 5 errata-xmlrpc 2021-04-21 13:26:20 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.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
Note You need to log in before you can comment on or make changes to this bug.