Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: Logging 5.2.1
Affects Version/s: Logging 5.2
Component/s: Log Storage
Labels:
- rn-done-resolved

Blocked:
False
Ready:
False
Docs QE Status:
NEW
QE Status:
NEW
Release Note Text:

Hide
Before this update, due to an issue in the release pipeline scripts, the value of the `olm.skipRange` field remained unchanged at `5.2.0` and was not updated when the z-stream number, `0`, increased. This update fixes the pipeline scripts to update the value of this field when the release numbers change.

Show
Before this update, due to an issue in the release pipeline scripts, the value of the `olm.skipRange` field remained unchanged at `5.2.0` and was not updated when the z-stream number, `0`, increased. This update fixes the pipeline scripts to update the value of this field when the release numbers change.

Sprint:
Logging (LogExp) - Sprint 207

SFDC Cases Links:
SFDC Cases Counter:

Description

That is clone bug to https://bugzilla.redhat.com/show_bug.cgi?id=2001742.

CSV: "elasticsearch-operator.5.0.7-27"
skipRange: ">=4.6.0-0 <5.0.0-27"
it should be ">=4.6.0-0 <5.0.7-27"

CSV: "elasticsearch-operator.5.1.1-36"
skipRange: ">=4.6.0-0 <5.1.0-36"
It should be ">=4.6.0-0 <5.1.1-36"

Attachments

Issue Links

clones

LOG-1741 ElasticSearch Operator isn't upgraded due to wrong olm.skipRange

Closed

Activity

People

Assignee:: Periklis Tsirakidis

Reporter:: Anping Li

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2021/09/10 12:21 PM

Updated:: 2022/03/14 7:30 PM

Resolved:: 2021/09/13 10:47 AM