Hide Forgot
Description of problem: Clusteroperator DEGRADED field is checking with "Degraded", but storage is using "Failing" https://github.com/openshift/api/pull/287/files Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-04-25-043235 How reproducible: Always Steps to Reproduce: 1. Deploy a new env on aws 2. Check clusteroperator status Actual results: $ oc get clusteroperator storage NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE storage 4.1.0-0.nightly-2019-04-25-002910 True False 45m $ oc get co storage -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-04-25T09:28:21Z" generation: 1 name: storage resourceVersion: "44624" selfLink: /apis/config.openshift.io/v1/clusteroperators/storage uid: 777a0879-673c-11e9-8f73-02f2ab250226 spec: {} status: conditions: - lastTransitionTime: "2019-04-25T10:14:24Z" status: "True" type: Available - lastTransitionTime: "2019-04-25T09:28:21Z" status: "False" type: Failing - lastTransitionTime: "2019-04-25T10:14:24Z" status: "False" type: Progressing extension: null relatedObjects: null versions: - name: operator version: 4.1.0-0.nightly-2019-04-25-043235 Expected results: Clusteroperator storage show proper value for DEGRADED
https://github.com/openshift/cluster-storage-operator/pull/29 has merged
verified with 4.1.0-0.nightly-2019-05-03-145222 $oc get clusteroperator storage NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE storage 4.1.0-0.nightly-2019-05-03-145222 True False False 6h20m
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:0758