-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
There is no error log inside gather.json of insights archive under the following 3 scenarios: + There are no extractor pods. + When the extractor pods return responses with 200 codes, but response contents are {}.
Version-Release number of selected component (if applicable):
How reproducible:
To create the same scenarios that are mentioned above.
Steps to Reproduce(Take the first scenario as an example.):
1. Delete all the insights-runtime-extractor pods. 2. Restarting IO immediately. 3. View the gather.json of Insights archive, check if this file includes some error logs about no extractor pods.
Actual results:
3. There are no error logs about no extractor pods inside gather.json file.
Expected results:
3. The gather.json file should include some error logs about no extractor pods.
Additional info:
The scenarios that are mentioned above belong to the same issue, but when verification, we should verify fixing in all the 3 scenarios.
- clones
-
OCPBUGS-55804 Expected error logs are not included in insights archive
-
- Verified
-
- depends on
-
OCPBUGS-55804 Expected error logs are not included in insights archive
-
- Verified
-
- links to
-
RHBA-2025:9278 OpenShift Container Platform 4.19.1 bug fix update