Bug 1953579

Summary: (release-4.7) Insights operator should collect related pod logs when operator is degraded
Product: OpenShift Container Platform Reporter: Ricardo Lüders <rluders>
Component: Insights OperatorAssignee: Ricardo Lüders <rluders>
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.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: The ClusterOperator Gather can now collect logs from pods that are related to unhealthy operators, and/or that are living in the same namespace that the operator. Reason: The insights operator should be able to determine the namespace associated with the operator and include pod logs in the bundle. Result: It is now collecting logs from unhealthy pods, not only related to the operator but from every pod that lives in the operator namespace.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-19 15:16:51 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: 1924663    
Bug Blocks: 1953582    

Description Ricardo Lüders 2021-04-26 12:24:20 UTC 
Description of problem:
Sometimes operators hit unexpected situation with pods being healthy - i.e. MCO can't rollout the config, but all pods are Running. In that case pod logs are not collected - and OTA team has to request must-gather from the customer.

Insights operator should be able to determine the namespace associated with the operator and include pod logs in the bundle
Comment 4 errata-xmlrpc 2021-05-19 15:16:51 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.7.11 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-2021:1550