Bug 1669258 - cluster-monitoring-operator clusteroperator flips indefinitely between progressing true and progressing false
Summary: cluster-monitoring-operator clusteroperator flips indefinitely between progre...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-24 19:00 UTC by Eric Paris
Modified: 2019-06-04 10:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-04 10:42:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:42:22 UTC

Description Eric Paris 2019-01-24 19:00:28 UTC 
We shouldn't do this if we aren't doing work...

apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: 2019-01-24T15:46:16Z
  generation: 1
  name: cluster-monitoring-operator
  resourceVersion: "102679"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/cluster-monitoring-operator
  uid: 2f24c9c4-1fef-11e9-b9f8-06e6bea067f2
spec: {}
status:
  conditions:
  - lastTransitionTime: 2019-01-24T15:50:42Z
    message: Successfully rolled out the stack.
    status: "True"
    type: Available
  - lastTransitionTime: 2019-01-24T18:17:11Z
    status: "False"
    type: Progressing
  - lastTransitionTime: 2019-01-24T15:50:42Z
    status: "False"
    type: Failing
  extension: null
  relatedObjects: null
  version: ""
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: 2019-01-24T15:46:16Z
  generation: 1
  name: cluster-monitoring-operator
  resourceVersion: "105176"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/cluster-monitoring-operator
  uid: 2f24c9c4-1fef-11e9-b9f8-06e6bea067f2
spec: {}
status:
  conditions:
  - lastTransitionTime: 2019-01-24T15:50:42Z
    message: Successfully rolled out the stack.
    status: "True"
    type: Available
  - lastTransitionTime: 2019-01-24T18:21:16Z
    message: Rolling out the stack.
    status: "True"
    type: Progressing
  - lastTransitionTime: 2019-01-24T15:50:42Z
    status: "False"
    type: Failing
  extension: null
  relatedObjects: null
  version: ""
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: 2019-01-24T15:46:16Z
  generation: 1
  name: cluster-monitoring-operator
  resourceVersion: "105767"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/cluster-monitoring-operator
  uid: 2f24c9c4-1fef-11e9-b9f8-06e6bea067f2
spec: {}
status:
  conditions:
  - lastTransitionTime: 2019-01-24T15:50:42Z
    message: Successfully rolled out the stack.
    status: "True"
    type: Available
  - lastTransitionTime: 2019-01-24T18:22:11Z
    status: "False"
    type: Progressing
  - lastTransitionTime: 2019-01-24T15:50:42Z
    status: "False"
    type: Failing
  extension: null
  relatedObjects: null
  version: ""
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: 2019-01-24T15:46:16Z
  generation: 1
  name: cluster-monitoring-operator
  resourceVersion: "108209"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/cluster-monitoring-operator
  uid: 2f24c9c4-1fef-11e9-b9f8-06e6bea067f2
spec: {}
status:
  conditions:
  - lastTransitionTime: 2019-01-24T15:50:42Z
    message: Successfully rolled out the stack.
    status: "True"
    type: Available
  - lastTransitionTime: 2019-01-24T18:26:16Z
    message: Rolling out the stack.
    status: "True"
    type: Progressing
  - lastTransitionTime: 2019-01-24T15:50:42Z
    status: "False"
    type: Failing
  extension: null
  relatedObjects: null
  version: ""
Comment 9 errata-xmlrpc 2019-06-04 10:42:15 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.