Summary: | [REF] Insights missing crash looping pods report | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Radek Vokál <rvokal> |
Component: | Insights Operator | Assignee: | Martin Kunc <mkunc> |
Status: | CLOSED DUPLICATE | QA Contact: | Angelina Vasileva <anikifor> |
Severity: | medium | Docs Contact: | Radek Vokál <rvokal> |
Priority: | unspecified | ||
Version: | unspecified | CC: | avicenzi, calfonso, dmisharo, mfojtik, mkunc |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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 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. 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? 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. 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. This is not a blocked for 4.5, moving to 4.5.0 |