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 2049505 - openSCAP scan failed with error Upload failed: Net::ReadTimeout
Summary: openSCAP scan failed with error Upload failed: Net::ReadTimeout
Keywords:
Status: CLOSED DUPLICATE of bug 1893672
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.10.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 11:16 UTC by isinghal
Modified: 2023-09-04 12:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-04 12:54:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
error message from UI (238.67 KB, image/png)
2022-02-25 08:05 UTC, isinghal 		no flags Details
ps (312.46 KB, image/png)
2022-02-25 08:07 UTC, isinghal 		no flags Details
top (295.52 KB, image/png)
2022-02-25 08:08 UTC, isinghal 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18334 0 None None None 2023-06-13 08:48:28 UTC

Description isinghal 2022-02-02 11:16:06 UTC 
Description of problem: Uploading openSCAP scan reports to satellite fails on 80% hosts when running on multiple hosts


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


How reproducible: Always


Steps to Reproduce:
1. Select 100 hosts on satellite and schedule openSCAP scan job
2. Monitor the job and see that most host fail


Actual results: While the scan runs fine, most hosts fail to upload result back to satellite with the error 'Upload failed: Net::ReadTimeout'. 


Expected results: All hosts should be scanned and report uploaded back to satellite.


Additional info: Looking the resources used during scan, we feel this may be an issue of excess memory usage by ruby due to reports being unzipped on satellite (we tested this on a 43G machine).
foreman-debug: http://perf54.perf.lab.eng.bos.redhat.com/pub/foreman-debug-vdtsw.tar.xz
Comment 1 isinghal 2022-02-25 08:05:07 UTC 
Created attachment 1863276 [details]
error message from UI
Comment 2 isinghal 2022-02-25 08:07:34 UTC 
Created attachment 1863277 [details]
ps
Comment 3 isinghal 2022-02-25 08:08:31 UTC 
Created attachment 1863278 [details]
top
Comment 4 Marek Hulan 2022-02-25 09:35:30 UTC 
Try to increase the timeout in /etc/foreman-proxy/settings.d/openscap.yml, if that helps it should be reconfigured through satellite-installer. When you schedule a scan on many machines like this, it's good to use the scheduling capability of the remote execution job. In the job form, click "Display advanced fields" and set either the Concurrency level or Time span. That should help keeping the load under control.
Comment 7 Brad Buckingham 2023-09-01 21:10:52 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 8 Ron Lavi 2023-09-04 12:54:56 UTC 
Marking it as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1893672
and the reason might be in https://bugzilla.redhat.com/show_bug.cgi?id=2237152 (not yet confirmed)

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