Bug 1845539

Summary:	Allow CLO and EO upgrades to 4.5 only from 4.4
Product:	OpenShift Container Platform	Reporter:	Periklis Tsirakidis <periklis>
Component:	Logging	Assignee:	Periklis Tsirakidis <periklis>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, qitang
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:06:02 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:	1845722

Description Periklis Tsirakidis 2020-06-09 13:26:57 UTC

Description of problem:
Upgrades to 4.5 require an 4.4 installation of cluster-logging-operator and elasticsearch-operator.


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

How reproducible:
- 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Anping Li 2020-06-10 13:03:10 UTC

No CSV Bundles

Comment 5 Qiaoling Tang 2020-06-15 06:12:11 UTC

In https://github.com/openshift/cluster-logging-operator/tree/master/manifests, the CSV version is 4.5, waiting for the manifests to be updated to 4.6.

Comment 6 Anping Li 2020-06-15 12:08:09 UTC

https://bugzilla.redhat.com/show_bug.cgi?id=1845722#c3. the upgrade fail as 4.4.0 > 4.4.0-2019xxxxx.

Comment 8 Anping Li 2020-06-16 03:18:41 UTC

If we don't use >=4.4.0-0, the CSV couldn't be upgraded.

it should be olm.skipRange: ">=4.4.0-0 <4.5.0" in clusterserviceversion.yaml and in art.yaml 
    - search: 'olm.skipRange: ">=4.4.0-0 <{MAJOR}.{MINOR}.0"'
      replace: 'olm.skipRange: ">=4.4.0-0 <{FULL_VER}"'
or
  olm.skipRange: ">=4.4.0 <4.5.0" in clusterserviceversion.yaml and in art.yaml 
    - search: 'olm.skipRange: ">=4.4.0 <{MAJOR}.{MINOR}.0"'
      replace: 'olm.skipRange: ">=4.4.0-0 <{FULL_VER}"'

Comment 9 Anping Li 2020-06-16 03:20:48 UTC

https://semver.org/, a check script: https://play.golang.org/p/H_kR0ZcVoaJ

Comment 10 Periklis Tsirakidis 2020-06-16 07:44:36 UTC

@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.

Comment 13 Anping Li 2020-06-17 01:59:12 UTC

Build catalogsource using 4.6 branch,  the clusterlogging and elasticsearch-operator csvs can be upgraded.

Comment 15 errata-xmlrpc 2020-10-27 16:06:02 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 (OpenShift Container Platform 4.6 GA Images), 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:4196