Bug 2026646

Summary: (release-4.8) Collect all the related container logs of a degraded cluster operator
Product: OpenShift Container Platform Reporter: Tomas Remes <tremes>
Component: Insights OperatorAssignee: Tomas Remes <tremes>
Status: CLOSED ERRATA QA Contact: Joao Fula <jfula>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.8CC: aos-bugs, dmisharo, hyagi, inecas, jfula, mklika, tremes
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2026644
: 2026659 (view as bug list) Environment:
Last Closed: 2021-12-14 11:45: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:
Bug Depends On: 2026644    
Bug Blocks: 2026659    

Comment 2 Joao Fula 2021-12-02 11:07:26 UTC
Verified on 4.8.0-0.nightly-2021-12-01-202737.
Verification steps:

1. Disable Cluster Version Operator.
2. Degrade Cluster Monitoring Operator:
Edit "config.yaml" key value in "cluster-monitoring-config" config map of "openshift-monitoring" namespace.
Put any non-valid yaml there.
3. Wait until Cluster Monitoring Operator will be degraded:
oc get co
4. Restart Insights Operator
5. Wait until a new archive will be created.
6. Download the archive.

config/pod/openshift-monitoring/logs contains logs for all containers of "openshift-monitoring" namespace.

Comment 5 errata-xmlrpc 2021-12-14 11:45:39 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 (OpenShift Container Platform 4.8.24 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.