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.
Bug 2018879 - Satellite inventory sync reports 504 error
Summary: Satellite inventory sync reports 504 error
Keywords:
Status: CLOSED DUPLICATE of bug 2127180
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-01 06:01 UTC by Dhananjay Pramod Mule
Modified: 2023-02-20 07:57 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-25 17:58:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6994782 0 None None None 2023-01-19 10:53:03 UTC

Description Dhananjay Pramod Mule 2021-11-01 06:01:59 UTC 
Description of problem:
Inventory sync on satellite causes 504 errors intermittently 

Version-Release number of selected component (if applicable):


How reproducible:
Intermittently 

Steps to Reproduce:
1.
2.
3.

Actual results:
~~~ /var/log/foreman/production.log
 Started GET "/redhat_access/r/insights/platform/inventory/v1/hosts?insights_id=XXXXXXX" for XX.XX.XX.XX at 2021-10-26 04:02:15 +0100
 Processing by InsightsCloud::Api::MachineTelemetriesController#forward_request as JSON
   Parameters: {"insights_id"=>"XXXXXXX", "path"=>"platform/inventory/v1/hosts"}
 Action failed
 Backtrace for 'Action failed' error (RestClient::GatewayTimeout): 504 Gateway Timeout
~~~


Expected results:
Inventory sync should be successful every-time  
~~~
 Started GET "/redhat_access/r/insights/platform/inventory/v1/hosts?insights_id=XXXXXXX" for XX.XX.XX.XX at 2021-10-26 04:02:35 +0100
 Processing by InsightsCloud::Api::MachineTelemetriesController#forward_request as JSON
   Parameters: {"insights_id"=>"XXXXXXX", "path"=>"platform/inventory/v1/hosts"}
 Completed 200 OK in 147ms (Views: 0.1ms | ActiveRecord: 2.0ms | Allocations: 5739)
~~~


Additional info:
Comment 4 Lindani Phiri 2021-11-02 13:57:59 UTC 
@Dhananjay
The URLs shown in the log snippet are related to insight client and not inventory sync.
Do we have more logs available?
Comment 5 Ben 2021-11-08 15:38:09 UTC 
I'm one of the end-users suffering from this.  What logs do you required?
Comment 15 Paul Dudley 2022-12-22 17:09:23 UTC 
Clearing needsinfo on dmule and adding logs here from an in-house example that directly matches a customer case. Logs are with debugging and REST requests also logged, should be helpful. Also setting severity to medium as I think this is affecting more customers than we realize/know of.
Comment 24 Shimon Shtein 2023-01-25 17:58:53 UTC 

*** This bug has been marked as a duplicate of bug 2127180 ***
Note You need to log in before you can comment on or make changes to this bug.