Bug 1669258

Summary: cluster-monitoring-operator clusteroperator flips indefinitely between progressing true and progressing false
Product: OpenShift Container Platform Reporter: Eric Paris <eparis>
Component: MonitoringAssignee: Sergiusz Urbaniak <surbania>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: fbranczy, surbania
Target Milestone: ---   
Target Release: 4.1.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-06-04 10:42:15 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:

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