Bug 1923888

Summary: Fixes error metadata gathering
Product: OpenShift Container Platform Reporter: Marcell Sevcsik <msevcsik>
Component: Insights OperatorAssignee: Marcell Sevcsik <msevcsik>
Status: CLOSED ERRATA QA Contact: Pavel Šimovec <psimovec>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, inecas, mklika, tremes
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: It was left up to Go on how to serialize the error objects. Consequence: Depending on the error, the error might show up as an empty string/object in the metadata, which is not helpful. Fix: Just storing the error string (ie.: error.Error()). Result: Errors are stored correctly in the metadata. (in the produced archive, under insights-operator/gathers.json)
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:57:46 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:

Description Marcell Sevcsik 2021-02-02 07:11:55 UTC
Description of problem:

Errors produced by the gather-functions are supposed to be stored in the metadata, but because it was left up to go on how to parse/store the errors, so they either showed up correctly or just an empty object, which is not really helpful.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 Pavel Šimovec 2021-02-04 07:31:30 UTC
internal change & tests passed

Comment 5 errata-xmlrpc 2021-02-24 15:57:46 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: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.