Description of problem: Check clusteroperator network, the Upgradeable ClusterStatusConditionType is missing. https://github.com/openshift/api/blob/master/config/v1/types_cluster_operator.go#L135 Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-06-30-221852 How reproducible: Always Steps to Reproduce: 1.Check clusteroperator network's detail. oc get co network -o yaml Actual results: ClusterOperator network missing ClusterStatusConditionType Upgradeable Expected results: ClusterStatusConditionType Upgradeable is there with proper value. Additional info: $ oc get co network -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-07-03T03:49:54Z" generation: 1 name: network resourceVersion: "11691" selfLink: /apis/config.openshift.io/v1/clusteroperators/network uid: 9e7c7cb2-9d45-11e9-945d-023561f97408 spec: {} status: conditions: - lastTransitionTime: "2019-07-03T03:49:55Z" status: "False" type: Degraded - lastTransitionTime: "2019-07-03T03:58:09Z" status: "False" type: Progressing - lastTransitionTime: "2019-07-03T03:51:25Z" status: "True" type: Available extension: null versions: - name: operator version: 4.2.0-0.nightly-2019-06-30-221852
At this point in time, the network operator is always upgradable. So I suppose we should just mark it as true.
Hi A PR addressing this has been merged: https://github.com/openshift/cluster-network-operator/pull/232 Best regards Alexander
Verified this bug on 4.2.0-0.nightly-2019-07-24-000310 - lastTransitionTime: "2019-07-24T02:29:55Z" status: "True" type: Upgradeable
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-2019:2922