Bug 1884764 - OLM incorrectly handling minKubeVersion
Summary: OLM incorrectly handling minKubeVersion
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Ben Luddy
QA Contact: Jian Zhang
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-02 18:51 UTC by Alan Conway
Modified: 2020-10-06 17:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-06 16:51:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Output of: oc describe clusterserviceversion/clusterlogging.v4.6.0 (21.53 KB, text/plain)
2020-10-02 18:51 UTC, Alan Conway
no flags Details

Description Alan Conway 2020-10-02 18:51:31 UTC
Created attachment 1718493 [details]
Output of: oc describe  clusterserviceversion/clusterlogging.v4.6.0

Description of problem:

Attempting to deploy a CSV with `minKubeVersion: 1.18.3` on a CRC cluster with `Kubernetes Version: v1.18.3+6c42de8` the deployment failed with

  - group: operators.coreos.com
    kind: ClusterServiceVersion
    message: CSV minKubeVersion (1.18.3) less than server version (v1.18.3+6c42de8)

Note the error messages says "minKubeVersion (1.18.3) less than server version" - the minKubeVersion is *supposed to be* less than or equal to the server version so this should not be an error. Possibly the "+6c42de8" (I guess that's a build identifier) is confusing the version parse and comparison?

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

[aconway@grommit org]$ crc version
CodeReady Containers version: 1.16.0+bf72d3a
OpenShift version: 4.5.9 (embedded in binary)
[aconway@grommit org]$ oc version
Client Version: 4.5.14
Server Version: 4.5.9
Kubernetes Version: v1.18.3+6c42de8

How reproducible:


Steps to Reproduce:
1. Create a cluster with 1.16.0+bf72d3a 
2. Deploy the CSV from https://github.com/openshift/cluster-logging-operator/blob/522e5d40/manifests/4.6/cluster-logging.v4.6.0.clusterserviceversion.yaml (I came across this in development)
3. oc describe  clusterserviceversion/clusterlogging.v4.6.0

Actual results:

Expected results:

Additional info:

Comment 1 Ben Luddy 2020-10-06 16:51:01 UTC
As you correctly stated, the minKubeVersion is supposed to be less than or equal to the server version. The ClusterServiceVersion's status is "Present", so the message you observed is informational.  A bit further down the requirement list, the missing requirement is a ServiceAccount:

  - group: ""
    kind: ServiceAccount
    message: Service account does not exist
    name: cluster-logging-operator
    status: NotPresent
    version: v1

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