Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1775630

Summary: There is no "olm.skipRange" in ptp-operator csv
Product: OpenShift Container Platform Reporter: huirwang
Component: NetworkingAssignee: zenghui.shi <zshi>
Networking sub component: ptp QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: cdc, zshi
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1776082 (view as bug list) Environment:
Last Closed: 2020-05-04 11:16:20 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: 1776082    

Description huirwang 2019-11-22 12:56:23 UTC 
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 3 zenghui.shi 2019-12-06 03:51:13 UTC 
move to modified as the PR fixing this issue is merged: https://github.com/openshift/ptp-operator/pull/26
Comment 12 errata-xmlrpc 2020-05-04 11:16:20 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:0581