Bug 1727032 - [4.2] ClusterOperator operator-lifecycle-manager missing ClusterStatusConditionType Upgradeable
Summary: [4.2] ClusterOperator operator-lifecycle-manager missing ClusterStatusConditi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Evan Cordell
QA Contact: Bruno Andrade
URL:
Whiteboard:
: 1727036 (view as bug list)
Depends On:
Blocks: 1743748
TreeView+ depends on / blocked
 
Reported: 2019-07-04 09:55 UTC by Liang Xia
Modified: 2019-10-16 06:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1743748 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:33:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:33:18 UTC

Description Liang Xia 2019-07-04 09:55:43 UTC
Description of problem:
Check clusteroperator operator-lifecycle-manager, 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 operator-lifecycle-manager's detail.
oc get co operator-lifecycle-manager -o yaml

Actual results:
ClusterOperator operator-lifecycle-manager missing ClusterStatusConditionType Upgradeable

Expected results:
ClusterStatusConditionType Upgradeable is there with proper value.

Additional info:
$ oc get co operator-lifecycle-manager -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2019-07-03T03:52:38Z"
  generation: 1
  name: operator-lifecycle-manager
  resourceVersion: "11016"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/operator-lifecycle-manager
  uid: fff8a79b-9d45-11e9-945d-023561f97408
spec: {}
status:
  conditions:
  - lastTransitionTime: "2019-07-03T03:52:38Z"
    status: "False"
    type: Degraded
  - lastTransitionTime: "2019-07-03T03:57:43Z"
    message: Deployed 0.10.1
    status: "False"
    type: Progressing
  - lastTransitionTime: "2019-07-03T03:52:38Z"
    status: "True"
    type: Available
  extension: null
  versions:
  - name: operator
    version: 4.2.0-0.nightly-2019-06-30-221852
  - name: operator-lifecycle-manager
    version: 0.10.1

Comment 1 Jian Zhang 2019-07-09 08:27:13 UTC
*** Bug 1727036 has been marked as a duplicate of this bug. ***

Comment 4 Bruno Andrade 2019-08-16 16:15:38 UTC
LGTM, Upgradeable is shown on OLM Cluster Operator.

oc exec olm-operator-798765b494-qpmkf -n openshift-operator-lifecycle-manager -- olm --version
OLM version: 0.11.0
git commit: 586e941bd1f42ea1f331453ed431fb43699fef70

oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-08-14-112500   True        False         33h     Cluster version is 4.2.0-0.nightly-2019-08-14-112500

$ oc get co operator-lifecycle-manager -o jsonpath='{range .status.conditions[*]}{.type}{"\n"}'
Degraded
Progressing
Available
Upgradeable

Marking as verified.

Comment 5 errata-xmlrpc 2019-10-16 06:33:07 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:2922


Note You need to log in before you can comment on or make changes to this bug.