Bug 1796315

Summary: [REF] Insights missing crash looping pods report
Product: OpenShift Container Platform Reporter: Radek Vokál <rvokal>
Component: Insights OperatorAssignee: Martin Kunc <mkunc>
Status: CLOSED DUPLICATE QA Contact: Angelina Vasileva <anikifor>
Severity: medium Docs Contact: Radek Vokál <rvokal>
Priority: unspecified    
Version: unspecifiedCC: avicenzi, calfonso, dmisharo, mfojtik, mkunc
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-14 12:46:47 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 Radek Vokál 2020-01-30 07:06:35 UTC
Insights missing crash looping pods report (at least our pods in openshift- namespaces)

Michal Fojtik will provide more details if needed.

Comment 1 Michal Fojtik 2020-01-30 10:07:30 UTC
Insights operator should be able to list all pods in all openshift-* namespaces and detect crashlooping pods and send it via telemetry payload.
We can start with listing all pods (as YAML) and filtering those that are not running or have restart count == 0.

Comment 2 Alexandre Vicenzi 2020-02-07 12:44:35 UTC
AFAIK this is the default behavior. We can look over to send this type of data, but I would consider this as a feature request with low priority and not a bug.

Any other thoughts?

Comment 3 Radek Vokál 2020-03-05 13:25:00 UTC
It is a feature request, let's discuss the priority based on your estimate to implement this. Feel free to create a jira card, link it here and close this bug.

Comment 4 Alexandre Vicenzi 2020-03-05 14:53:23 UTC
I will leave this open until we plan what to do. As this is RFE we need first to evaluate the value of such data.

Comment 5 Martin Kunc 2020-06-01 05:03:57 UTC
This is not a blocked for 4.5, moving to 4.5.0