Bug 1845722
| Summary: | Allow CLO and EO upgrades to 4.5 only from 4.4 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Logging | Assignee: | Periklis Tsirakidis <periklis> |
| Status: | CLOSED ERRATA | QA Contact: | Giriyamma <gkarager> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.5 | CC: | anli, aos-bugs, gkarager |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:43:40 UTC | Type: | --- |
| 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: | 1845539 | ||
| Bug Blocks: | |||
|
Description
OpenShift BugZilla Robot
2020-06-09 21:28:49 UTC
The skipRange is wrong. It should be olm.skipRange: ">=4.4.0-0 <4.5.0" in clusterserviceversion.yaml. channels: - currentCSV: clusterlogging.4.2.34-202006110619 name: '4.2' - currentCSV: clusterlogging.4.1.45-202005160309 name: preview - currentCSV: clusterlogging.4.3.25-202006081335 name: '4.3' - currentCSV: clusterlogging.4.2.34-202006110619-s390x name: 4.2-s390x - currentCSV: clusterlogging.4.4.0-202006080610 name: '4.4' - currentCSV: clusterlogging.4.5.0-202006101338 name: '4.5' defaultChannel: '4.5' packageName: cluster-logging I have tested the CLO and EO upgrade from 4.4 to 4.5. Moving this bug to verified as the upgrades are successful. Below are the testing results: Before upgrade: $ oc get sub -n openshift-logging NAME PACKAGE SOURCE CHANNEL cluster-logging cluster-logging qe-app-registry 4.4 $ oc get sub -n openshift-operators-redhat NAME PACKAGE SOURCE CHANNEL elasticsearch-operator elasticsearch-operator qe-app-registry 4.4 $ oc get csv -n openshift-logging NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.4.0-202006080610 Cluster Logging 4.4.0-202006080610 Succeeded elasticsearch-operator.4.4.0-202006080610 Elasticsearch Operator 4.4.0-202006080610 Succeeded After upgrade: $ oc get sub -n openshift-logging NAME PACKAGE SOURCE CHANNEL cluster-logging cluster-logging qe-app-registry 4.5 $ oc get sub -n openshift-operators-redhat NAME PACKAGE SOURCE CHANNEL elasticsearch-operator elasticsearch-operator qe-app-registry 4.5 $ oc get csv -n openshift-logging NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.5.0-202006101338 Cluster Logging 4.5.0-202006101338 clusterlogging.4.4.0-202006080610 Succeeded elasticsearch-operator.4.5.0-202006101717 Elasticsearch Operator 4.5.0-202006101717 elasticsearch-operator.4.4.0-202006080610 Succeeded $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-06-11-183238 True False 18h Cluster version is 4.5.0-0.nightly-2020-06-11-183238 @Anping The -0 is just a build timestamp and it should not be part of the version check at all. Semver doesn't know anything about build timestamps or so like. If the installation does not proceed please re-eval/contact OLM team. Verified on clusterlogging-4.5.0-202006180838 and elasticsearch-operator 4.5.0-202006180838 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 |