Bug 1841057

Summary: After the start the upload of results shouldn't be delayed
Product: OpenShift Container Platform Reporter: Martin Kunc <mkunc>
Component: Insights OperatorAssignee: Martin Kunc <mkunc>
Status: CLOSED ERRATA QA Contact: Angelina Vasileva <anikifor>
Severity: medium Docs Contact: Radek Vokál <rvokal>
Priority: unspecified    
Version: 4.5CC: avicenzi, inecas
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1841058 1855212 1855240 (view as bug list) Environment:
Last Closed: 2020-07-13 17:42:23 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:
Bug Depends On:    
Bug Blocks: 1841058, 1841059, 1841064, 1842489, 1855212    

Description Martin Kunc 2020-05-28 09:05:27 UTC
Description of problem:
Currently for protection against thundering herd the upload of collected data is delayed (15-30 min) of 2h collecting interval. We would like to get first data sooner, so if the IO is starting for first time, or when it is running successfully, initial upload wont be delayed.

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

How reproducible:
After the installation the IO archive appears in DataHub too late.

Steps to Reproduce:
1. Install OC
2. Keep checking DataHub support shell folder

Actual results:
Archive was created with significant delay ~50 min.

Expected results:
Archive should be there as soon as possible.

Additional info:

Comment 3 Angelina Vasileva 2020-06-02 08:02:13 UTC
Fixed and verified in 4.5.0-0.nightly-2020-06-02-044312

I0602 07:24:33.609983       1 insightsuploader.go:87] Reporting status periodically to https://cloud.redhat.com/api/ingress/v1/upload every 2h0m0s, starting in 0s
I0602 07:24:49.667517       1 insightsclient.go:214] Successfully reported id=2020-06-02T07:24:48Z x-rh-insights-request-id=17a26aa845604c17b1f443f04f2f6f23, wrote=42699

Comment 4 errata-xmlrpc 2020-07-13 17:42:23 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.