Bug 1860397 - Nodes going notReady because of unknown Reason
Summary: Nodes going notReady because of unknown Reason
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-controller-manager
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.z
Assignee: Gabe Montero
QA Contact: wewang
Depends On: 1852964
Blocks: 1861874
TreeView+ depends on / blocked
Reported: 2020-07-24 13:07 UTC by Gabe Montero
Modified: 2020-08-10 13:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: intermittent availability issues with the apiserver could lead to intermittent issues with the openshift controller manager operator retrieving deployments it manages Consequence: a failure to retrieve a deployment at the wrong moment resulted in the openshift controller manager operator making a nil reference that results in a panic in the operator Fix: nil reference checks are now in place to handle this error condition, report it, but also retry again per expected controller operations. Result: openshift controller manager operator properly handles intermittent issues retrieving deployments from the api server.
Clone Of: 1852964
: 1861874 (view as bug list)
Last Closed: 2020-08-10 13:50:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-openshift-controller-manager-operator pull 164 0 None closed [release-4.5] Bug 1860397: account for nil DaemonSet returned from library-go 2020-10-20 13:09:51 UTC
Red Hat Product Errata RHBA-2020:3188 0 None None None 2020-08-10 13:50:39 UTC

Comment 5 errata-xmlrpc 2020-08-10 13:50:20 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.5.5 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.


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