Bug 1781104 - Failed pods should not trigger KubePodNotReady
Summary: Failed pods should not trigger KubePodNotReady
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1781103
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 10:43 UTC by Sergiusz Urbaniak
Modified: 2020-01-23 11:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1781103
Environment:
Last Closed: 2020-01-23 11:18:16 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 583 'None' 'open' 'Bug 1781104: revert failed pod marked as NotReady ' 2019-12-09 10:46:04 UTC
Red Hat Product Errata RHBA-2020:0062 None None None 2020-01-23 11:18:41 UTC

Description Sergiusz Urbaniak 2019-12-09 10:43:08 UTC
+++ This bug was initially created as a clone of Bug #1781103 +++

Upstream tried to fix https://github.com/kubernetes-monitoring/kubernetes-mixin/issues/215 by contributing https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/221.

Unfortunately this is not the right approach and it was reverted in https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/296.

release-4.4 does contain the revert, but release-4.3 doesn't.

Comment 4 errata-xmlrpc 2020-01-23 11:18:16 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, 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-2020:0062


Note You need to log in before you can comment on or make changes to this bug.