Bug 1756283

Summary: [sriov] sriov operator tag should be use 4.2 not latest
Product: OpenShift Container Platform Reporter: zhaozhanqi <zzhao>
Component: NetworkingAssignee: Feng Pan <fpan>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: high CC: bbennett, pliu
Version: 4.2.0   
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1756471 (view as bug list) Environment:
Last Closed: 2019-10-16 06:41:50 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: 1756471    
Bug Blocks:    

Description zhaozhanqi 2019-09-27 09:20:32 UTC
Description of problem:
in https://github.com/openshift/sriov-network-operator/blob/release-4.2/manifests/4.2/sriov-network-operator.v0.0.1.clusterserviceversion.yaml#L252

the sirov operator tag is latest. when install sriov operator using the rh-osbs-operators registry. it will not use the correct image

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


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:

quay.io/openshift/origin-sriov-network-operator:latest

Expected results:

quay.io/openshift/origin-sriov-network-operator:4.2

Additional info:

Comment 1 Peng Liu 2019-09-27 12:58:19 UTC
(In reply to zhaozhanqi from comment #0)
> Description of problem:
> in
> https://github.com/openshift/sriov-network-operator/blob/release-4.2/
> manifests/4.2/sriov-network-operator.v0.0.1.clusterserviceversion.yaml#L252
> 
> the sirov operator tag is latest. when install sriov operator using the
> rh-osbs-operators registry. it will not use the correct image
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1. 
> 2.
> 3.
> 
> Actual results:
> 
> quay.io/openshift/origin-sriov-network-operator:latest
> 
> Expected results:
> 
> quay.io/openshift/origin-sriov-network-operator:4.2
> 
> Additional info:

Please create a BZ for 4.3, so we can get the fix merged in master, then backport to 4.2

Comment 2 Peng Liu 2019-09-27 14:58:40 UTC
Ignore my last comment. No BZ needed for 4.3.

Comment 4 Peng Liu 2019-09-27 15:20:10 UTC
PR for branch release-4.2 https://github.com/openshift/sriov-network-operator/pull/85 
According to ART team, the 4.2 operator bundle directory shall be removed in master for 4.3, so it is not a backport. This PR is for 4.2 branch only.

Comment 7 errata-xmlrpc 2019-10-16 06:41:50 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-2019:2922