Description of problem: The Node Tuning Operator (alongside with a few other SLOs) currently uses leader-for-life implementation from operator-sdk, which already caused several known upgrade failures (rhbz#1916865, rhbz#1958885) due to ConfigMap lock not being removed by the k8s garbage collection mechanism. Version-Release number of selected component (if applicable): All currently supported versions. How reproducible: Rare, but serious as it causes cluster upgrade failures. Steps to Reproduce: This is unfortunately hard to reproduce. Actual results: NTO stuck waiting for a ConfigMap lock to be removed. Expected results: NTO should not rely on the k8s GC mechanism for leader election. Additional info: Upstream fix: https://github.com/openshift/cluster-node-tuning-operator/pull/229 Related BZs: https://bugzilla.redhat.com/show_bug.cgi?id=1916865 https://bugzilla.redhat.com/show_bug.cgi?id=1958885
Cluster version: 4.8.0-0.nightly-2021-05-26-071911 Impossible to reproduce. Regression tests 100% passed.
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438