Bug 1776082 - There is no "olm.skipRange" in ptp-operator csv
Summary: There is no "olm.skipRange" in ptp-operator csv
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3.z
Assignee: zenghui.shi
QA Contact: huirwang
URL:
Whiteboard:
Depends On: 1775630
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-25 05:59 UTC by zenghui.shi
Modified: 2020-02-19 05:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1775630
Environment:
Last Closed: 2020-02-19 05:39:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ptp-operator pull 23 0 'None' closed [release-4.3] BUG 1776082: allow updating operator to latest entry in channel 2020-07-16 01:31:28 UTC
Github openshift ptp-operator pull 27 0 'None' closed [release-4.3] BUG 1776082: fix olm.skipRange version 2020-07-16 01:31:28 UTC
Github openshift ptp-operator pull 29 0 None closed [release-4.3] Bug 1776082: support pre-release version upgrade in olm.skipRange 2020-07-16 01:31:28 UTC
Red Hat Product Errata RHBA-2020:0492 0 None None None 2020-02-19 05:40:03 UTC

Description zenghui.shi 2019-11-25 05:59:31 UTC
+++ This bug was initially created as a clone of Bug #1775630 +++

Description of problem:
There is no "olm.skipRange" in ptp-operator csv



Version-Release number of selected component (if applicable):
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.3.0-201911212330-ose-ptp-operator

How reproducible:
always

Steps to Reproduce:
1.Install ptp-operator from web consoel
2.Check ptp-operator csv
3.
huiran-mac:script hrwang$ oc get csv -o yaml -n openshift-ptp | grep "olm.skipRange"
huiran-mac:script hrwang$ 

Actual results:
Due to there is no "olm.skipRange" in ptp-operator csv, will cause ptp-operator cannot upgrade.

Expected results:
There should have "olm.skipRange" in ptp-operator csv

Additional info:

Comment 4 huirwang 2019-12-12 06:16:36 UTC
huiran-mac:script hrwang$ oc get csv -o yaml -n openshift-ptp | grep skip
      olm.skipRange: '>=4.3.0 <4.3.0-201912080037'

Comment 5 huirwang 2019-12-17 05:08:31 UTC
Currently it seems still something wrong in the ptp manifests, it still cannot upgrade.


huiran-mac:script hrwang$ oc get csv -n openshift-ptp
NAME                              DISPLAY        VERSION   REPLACES             PHASE
descheduler.v0.0.4                Descheduler    0.0.4     descheduler.v0.0.3   Succeeded
ptp-operator.4.3.0-201912080037   PTP Operator   4.3.0               

sh-4.2$ cd ptp-operator-8i8x9i0d/
sh-4.2$ ls
4.3  4.4  ptp-operator.package.yaml
sh-4.2$ cat ptp-operator.package.yaml 
channels:
- currentCSV: ptp-operator.4.3.0-201912130552
  name: 4.3
- currentCSV: ptp-operator.4.4.0-201912130715
  name: '4.4'
defaultChannel: '4.4'
packageName: ptp-operator
sh-4.2$ ls
4.3  4.4  ptp-operator.package.yaml

4.3.0-201912130552 is higher than 4.3.0-201912080037, but still not upgrade.

Comment 9 huirwang 2019-12-19 10:16:08 UTC
Just checked the skipRange is changed. Need sometime to wait for new ptp-operator version
huiran-mac:script hrwang$ oc get csv -o yaml -n openshift-ptp | grep skip
      olm.skipRange: '>=4.3.0-0 <4.3.0-201912180717'

huiran-mac:script hrwang$ oc get csv -n openshift-ptp
NAME                              DISPLAY        VERSION   REPLACES             PHASE
ptp-operator.4.3.0-201912180717   PTP Operator   4.3.0                          Succeeded

Comment 13 huirwang 2020-02-07 10:31:59 UTC
Verified 
ptp-operator.4.3.0-202001211731             PTP Operator             4.3.0                                                            Replacing
ptp-operator.4.3.1-202002040740             PTP Operator             4.3.0                ptp-operator.4.3.0-202001211731             Installing
ptp-operator.4.3.1-202002040740             PTP Operator             4.3.0                ptp-operator.4.3.0-202001211731             Succeeded

Comment 15 errata-xmlrpc 2020-02-19 05:39:53 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, 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:0492


Note You need to log in before you can comment on or make changes to this bug.