Bug 1740665 - [sriov] should use 'v1' instead of 'v1alpha2'
Summary: [sriov] should use 'v1' instead of 'v1alpha2'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.2.0
Hardware: All
OS: All
medium
low
Target Milestone: ---
: 4.2.0
Assignee: Peng Liu
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-13 12:45 UTC by zhaozhanqi
Modified: 2019-10-16 06:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:35:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 64 0 None None None 2019-08-15 05:17:59 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:36:06 UTC

Description zhaozhanqi 2019-08-13 12:45:54 UTC 
Description of problem:
In install sriov operator webconsole. the following apiVersion should use 'v1' instead of 'v1alpha2'

oc create -f - <<EOF
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: sriov-network-operators
  namespace: sriov-network-operator
spec:
  targetNamespaces:
  - sriov-network-operator
EOF

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


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 zhaozhanqi 2019-08-22 05:53:46 UTC 
Verified this bug with https://github.com/openshift/sriov-network-operator/pull/64/files
Comment 3 errata-xmlrpc 2019-10-16 06:35: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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.