Bug 1727015
Summary: | [4.2] ClusterOperator cluster-autoscaler missing ClusterStatusConditionType Upgradeable | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Liang Xia <lxia> |
Component: | Cloud Compute | Assignee: | Brad Ison <brad.ison> |
Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.0 | CC: | agarcial, zhsun |
Target Milestone: | --- | ||
Target Release: | 4.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-16 06:33:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Liang Xia
2019-07-04 09:18:57 UTC
verified clusterversion: 4.2.0-0.nightly-2019-08-05-223032 $ oc get clusteroperator cluster-autoscaler -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-08-05T05:57:41Z" generation: 1 name: cluster-autoscaler resourceVersion: "329962" selfLink: /apis/config.openshift.io/v1/clusteroperators/cluster-autoscaler uid: efe13380-b745-11e9-998d-02f285780c3c spec: {} status: conditions: - lastTransitionTime: "2019-08-05T05:57:41Z" message: at version 4.2.0-0.nightly-2019-08-05-223032 status: "True" type: Available - lastTransitionTime: "2019-08-06T01:16:27Z" status: "False" type: Progressing - lastTransitionTime: "2019-08-05T05:57:41Z" status: "False" type: Degraded - lastTransitionTime: "2019-08-06T01:16:12Z" status: "True" type: Upgradeable extension: null relatedObjects: - group: "" name: openshift-machine-api resource: namespaces versions: - name: operator version: 4.2.0-0.nightly-2019-08-05-223032 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 |