Bug 1843923
| Summary: | After the start the upload of results shouldn't be delayed - release 4.3 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Insights Operator | Assignee: | Martin Kunc <mkunc> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Šimovec <psimovec> |
| Severity: | medium | Docs Contact: | Radek Vokál <rvokal> |
| Priority: | high | ||
| Version: | 4.5 | CC: | avicenzi, inecas, mkunc |
| Target Milestone: | --- | ||
| Target Release: | 4.3.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
The Insights Operator is only uploading data after first polling interval, (2h+-15m).
Consequence:
The data collected by Insights Op. are then not available instantly. The Insishgts data available in OCM are then delayed.
Fix:
This fix is changing uploading logic to upload the data as soon as they are collected for the first time. The logic for consequent uploads isn't changing.
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-23 13:52:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1842489 | ||
| Bug Blocks: | 1841064, 1843924 | ||
|
Comment 1
Martin Kunc
2020-06-04 12:24:50 UTC
The faster data collection will be important for CEE organization ("support"), increasing priority to High.
Version 4.3.0-0.nightly-2020-09-12-071205 I used test/integration/bugs_test.go::TestUploadNotDelayedAfterStart First try: could not verify -> Fast upload was not enabled, because "The last pod state is unhealthy".. so the upload took ~40 minutes, with the unhealthy pod given it worked as expected I discused this with Martin and he found the cause of failure - a new Jira task will be created for that problem Second try: provisioned cluster again, this time I did get healthy pod and test passed with message: "Archive upload delay was 37 seconds" -> this BZ is verified 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 (OpenShift Container Platform 4.3.38 bug fix update), 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/RHBA-2020:3609 |