Bug 1802934
| Summary: | Cluster-logging-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. | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> | |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.3.z | CC: | anli, aos-bugs, jokerman, wking | |
| Target Milestone: | --- | |||
| Target Release: | 4.3.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1802935 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-10 23:53:52 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: | 1802935 | |||
| Bug Blocks: | ||||
The elasticsearch CSV wasn't fixed. elasticsearch-operator/4.3/elasticsearch-operator.v4.3.0.clusterserviceversion.yaml: olm.skipRange: ">=4.2.0 <4.3.0" elasticsearch-operator/4.4/elasticsearch-operator.v4.4.0.clusterserviceversion.yaml: olm.skipRange: ">=4.1.0 <4.4.0-202002210654" cluster-logging/4.3/cluster-logging.v4.3.0.clusterserviceversion.yaml: olm.skipRange: ">=4.1.0 <4.3.4-202002210552" cluster-logging/4.4/cluster-logging.v4.4.0.clusterserviceversion.yaml: olm.skipRange: ">=4.1.0 <4.4.0-202002210654" (In reply to Anping Li from comment #4) > The elasticsearch CSV wasn't fixed. > > elasticsearch-operator/4.3/elasticsearch-operator.v4.3.0. > clusterserviceversion.yaml: olm.skipRange: ">=4.2.0 <4.3.0" EO resolved by https://bugzilla.redhat.com/show_bug.cgi?id=1803145 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:0676 |
Description of problem: Cluster-logging-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/cluster-logging/4.3/cluster-logging.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: # The version value is substituted by the ART pipeline name: clusterlogging.4.3.2-202002122007 namespace: placeholder annotations: capabilities: Seamless Upgrades categories: "OpenShift Optional, Logging & Tracing" certified: "false" description: |- The Cluster Logging Operator for OKD provides a means for configuring and managing your aggregated logging stack. containerImage: image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-logging-operator:v4.3.2 createdAt: 2018-08-01T08:00:00Z support: AOS Logging # The version value is substituted by the ART pipeline olm.skipRange: ">=4.2.0 <4.3.0" Version-Release number of selected component (if applicable): clusterlogging.4.3.2-202002122007 How reproducible: Always Steps to Reproduce: 1. deploy cluster-logging-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: