Bug 1827775

Summary: Typo in Upgradable False Condition
Product: OpenShift Container Platform Reporter: Shawn Hurley <shurley>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OperatorHub QA Contact: yhui
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: wking
Version: 4.4   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1827777 (view as bug list) Environment:
Last Closed: 2020-07-13 17:31:30 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:
Bug Depends On:    
Bug Blocks: 1827777    

Description Shawn Hurley 2020-04-24 18:49:42 UTC
Description of problem:
      message: 'Cluster operator marketplace cannot be upgraded: The cluster has custom
        OperatorSource/CatalogSourceConfig, which are deprecated in future versions.
        Please visit this link for further deatils: https://docs.openshift.com/container-platform/4.4/release_notes/ocp-4-4-release-notes.html#ocp-4-4-marketplace-apis-deprecated'
      reason: DprecatedAPIsInUse


s/DprecatedAPIsInUse/DeprecatedAPIsInUse/g
s/deatils/details/g


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 W. Trevor King 2020-04-25 15:01:46 UTC
You'll also need at least the "deatils" -> "details" portion of https://github.com/operator-framework/operator-marketplace/pull/302/files#diff-a5666326aefdf43a8e89fd4871449fa0L58

Comment 5 yhui 2020-04-26 04:21:37 UTC
Version:
[hui@localhost work]$ oc version
Client Version: 4.5.0-202004062101-f2b01c4
Server Version: 4.5.0-0.nightly-2020-04-25-170442
Kubernetes Version: v1.18.0-rc.1
[hui@localhost work]$ oc exec catalog-operator-57f779987b-7fls6 -n openshift-operator-lifecycle-manager -- olm --version
OLM version: 0.14.2
git commit: 280a2a64115aa0388c11c5472188cd3169e05661

Steps:
[hui@localhost ~]$ oc get clusteroperator marketplace -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2020-04-26T03:39:19Z"
  generation: 1
  name: marketplace
  resourceVersion: "26535"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/marketplace
  uid: dbb76576-34f6-415b-8462-c0001b0b7109
spec: {}
status:
  conditions:
  - lastTransitionTime: "2020-04-26T03:52:05Z"
    message: 'Successfully progressed to release version: 4.5.0-0.nightly-2020-04-25-170442'
    reason: OperatorAvailable
    status: "False"
    type: Progressing
  - lastTransitionTime: "2020-04-26T04:09:08Z"
    message: 'The cluster has custom OperatorSource, which is deprecated in future
      versions. Please visit this link for further details: https://docs.openshift.com/container-platform/4.4/release_notes/ocp-4-4-release-notes.html#ocp-4-4-marketplace-apis-deprecated'
    reason: DeprecatedAPIsInUse
    status: "False"
    type: Upgradeable
  - lastTransitionTime: "2020-04-26T03:52:05Z"
    message: 'Available release version: 4.5.0-0.nightly-2020-04-25-170442'
    reason: OperatorAvailable
    status: "True"
    type: Available
  - lastTransitionTime: "2020-04-26T03:51:45Z"
    message: Current CR sync ratio (1) meets the expected success ratio (0.3)
    reason: OperandTransitionsSucceeding
    status: "False"
    type: Degraded
  extension: null
  relatedObjects:
  - group: ""
    name: openshift-marketplace
    resource: namespaces
  - group: operators.coreos.com
    name: ""
    namespace: openshift-marketplace
    resource: OperatorSource
  - group: operators.coreos.com
    name: ""
    namespace: openshift-marketplace
    resource: CatalogSource
  versions:
  - name: operator
    version: 4.5.0-0.nightly-2020-04-25-170442

The typo has been fixed.

Comment 6 errata-xmlrpc 2020-07-13 17:31:30 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-2020:2409