+++ This bug was initially created as a clone of Bug #1802934 +++

Description of problem:
Elasticsearch-operator couldn't upgrade from 4.3.1 to 4.3.2 due to `olm.skipRange: ‘>=4.2.0 <4.3.0’` in the csv file.

I think it should be ` olm.skipRange: ">=4.2.0 <4.3.2-xxxxxxxx"`

$ cat tempdir/manifests/elasticsearch-operator/4.3/elasticsearch-operator.v4.3.0.clusterserviceversion.yaml 
#! validate-crd: deploy/chart/templates/0000_30_02-clusterserviceversion.crd.yaml
#! parse-kind: ClusterServiceVersion
apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  name: elasticsearch-operator.4.3.2-202002122007
  namespace: placeholder
  annotations:
    categories: "OpenShift Optional, Logging & Tracing"
    capabilities: "Seamless Upgrades"
    certified: "false"
    description: |-
      The Elasticsearch Operator for OKD provides a means for configuring and managing an Elasticsearch cluster for tracing and cluster logging.
      ## Prerequisites and Requirements
      ### Elasticsearch Operator Namespace
      The Elasticsearch Operator must be deployed to the global operator group namespace
      ### Memory Considerations
      Elasticsearch is a memory intensive application.  The initial
      set of OKD nodes may not be large enough to support the Elasticsearch cluster.  Additional OKD nodes must be added
      to the OKD cluster if you desire to run with the recommended (or better) memory. Each ES node can operate with a
      lower memory setting though this is not recommended for production deployments.
    containerImage: image-registry.openshift-image-registry.svc:5000/openshift/ose-elasticsearch-operator:v4.3.2
    createdAt: 2019-02-20T08:00:00Z
    support: AOS Cluster Logging, Jaeger
    olm.skipRange: ">=4.2.0 <4.3.0"
    alm-examples: |-
        [



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

How reproducible:
Always

Steps to Reproduce:
1. deploy elasticsearch-operator 4.3.1-202002032140 via OLM
2. then try to upgrade it to 4.3.2-202002122007
3.

Actual results:
The operator isn't upgraded, it still 4.3.1

Expected results:


Additional info: