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:
(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
Ignore my last comment. No BZ needed for 4.3.
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.
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