the static pod operator directly sets available and progressing, which makes it impossible to appropriately compose the conditions inside of an operator.
All PRs merged, moving to modified.
This bug library code is https://github.com/openshift/library-go/pull/704 , which is bumped into KAS, KCM, KSCH. Ying, Kasturi, please better to help check KCM and KSCH respectively while we'll check KAS, thx
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-02-19-173908 True False 6h Cluster version is 4.4.0-0.nightly-2020-02-19-173908 Per PR changes of https://github.com/openshift/cluster-kube-apiserver-operator/pull/754, defined new StaticPodsAvailableConditionType:"StaticPodsAvailable" and NodeInstallerProgressingConditionType:"NodeInstallerProgressing", checked in below operators, For KAS, $ oc get kubeapiservers.operator.openshift.io/cluster -o yaml | grep -E 'NodeInstallerProgressing|StaticPodsAvailable' type: StaticPodsAvailable type: NodeInstallerProgressing For KSCH, $ oc get kubescheduler/cluster -o yaml | grep -E 'NodeInstallerProgressing|StaticPodsAvailable' type: StaticPodsAvailable type: NodeInstallerProgressing For KCM, $ oc get kubecontrollermanagers.operator.openshift.io/cluster -o yaml | grep -E 'NodeInstallerProgressing|StaticPodsAvailable' type: StaticPodsAvailable type: NodeInstallerProgressing The above two condition type were found as expected, move the bug to verify.
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:0581